monitoring tool

Are there any good monitoring tools that would notify us upon CPU,Disk
space, blocking, errors/warnings in event logs,etc..
We use Sitescope and it doesnt seem to be a robust tool
Thanks
Hi,
Have a look into Microsoft operation manager (MOM). See the below URL for
details:-
http://www.microsoft.com/mom/default.mspx
Thanks
Hari
SQL Server MVP
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:OESfJu$qFHA.460@.TK2MSFTNGP15.phx.gbl...
> Are there any good monitoring tools that would notify us upon CPU,Disk
> space, blocking, errors/warnings in event logs,etc..
> We use Sitescope and it doesnt seem to be a robust tool
> Thanks
>
|||There are a lot of different monitoring tools. MOM is one
that Hari mentioned. You may also want to look at some of
the tools from idera:
www.idera.com
-Sue
On Sun, 28 Aug 2005 11:08:46 -0700, "Hassan"
<hassanboy@.hotmail.com> wrote:

>Are there any good monitoring tools that would notify us upon CPU,Disk
>space, blocking, errors/warnings in event logs,etc..
>We use Sitescope and it doesnt seem to be a robust tool
>Thanks
>
|||Take a look at AgileInfoSoftware DataStudio, under its Performance
Monitoring node, it allows user to monitor process, lock, blocking locks
etc.
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:OESfJu$qFHA.460@.TK2MSFTNGP15.phx.gbl...
> Are there any good monitoring tools that would notify us upon CPU,Disk
> space, blocking, errors/warnings in event logs,etc..
> We use Sitescope and it doesnt seem to be a robust tool
> Thanks
>
|||Check out AgileInfoSoftware DataStudio http://www.agileinfollc.com
John King
AgileInfoSoftware
http://www.agileinfollc.com
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:OESfJu$qFHA.460@.TK2MSFTNGP15.phx.gbl...
> Are there any good monitoring tools that would notify us upon CPU,Disk
> space, blocking, errors/warnings in event logs,etc..
> We use Sitescope and it doesnt seem to be a robust tool
> Thanks
>
|||Sorry to bring back an old thread, but this is of great interest to me also.
I'm doing a trial deployment of MOM and finding it a bit more than we may
need. I like the extensibility via the management packs, but it may be too
big, too expensive and to tell the truth, a bit 'finicky' in setting up and
maintaining. Right now I have more alerts about MOM itself to figure out and
fix than the SQL servers we are attempting to monitor.
I'm a network engineer, not a SQL DBA. All I really want is something that
alerts when a job fails, lets us know if the SQL Agent isn't running and a
few other server statistics.
I'm going to look into Idera and Agileinfo.
Does anyone have any other recomendations? I know vendors like to throw in
the kitchen sink when it comes to features. In this case, for me, KISS is
more like my guiding principle.
Regards,
MK
"John King" wrote:

> Check out AgileInfoSoftware DataStudio http://www.agileinfollc.com
> John King
> AgileInfoSoftware
> http://www.agileinfollc.com
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:OESfJu$qFHA.460@.TK2MSFTNGP15.phx.gbl...
>
>
|||I really like Idera's Diagnostic Manager. Great third-party tool!
Lori
"Michael Kenny" <MichaelKenny@.discussions.microsoft.com> wrote in message
news:CA9FCD26-8BB7-4247-930F-2F803688233E@.microsoft.com...[vbcol=seagreen]
> Sorry to bring back an old thread, but this is of great interest to me
> also.
> I'm doing a trial deployment of MOM and finding it a bit more than we may
> need. I like the extensibility via the management packs, but it may be too
> big, too expensive and to tell the truth, a bit 'finicky' in setting up
> and
> maintaining. Right now I have more alerts about MOM itself to figure out
> and
> fix than the SQL servers we are attempting to monitor.
>
> I'm a network engineer, not a SQL DBA. All I really want is something that
> alerts when a job fails, lets us know if the SQL Agent isn't running and a
> few other server statistics.
> I'm going to look into Idera and Agileinfo.
> Does anyone have any other recomendations? I know vendors like to throw in
> the kitchen sink when it comes to features. In this case, for me, KISS is
> more like my guiding principle.
> Regards,
> MK
>
>
> "John King" wrote:

Monitoring blocking...

Is there a way to be notified automatically when blocking
occurs (either via net send or e-mail and maybe even have
that written to the NT event log)?
ThanksHi Rob
Blocking happens all the time, but it is usually for so short a period of
time that if you had a notification every time you thing there was another
spam virus. There is no automatic way to e notified about blocking, but here
are some avenues you might consider:
Set up a script to run a loop, that captures sysprocesses output and saves
it in a table. Compare the waittime column from one run to the next, if the
blocked column is >0. If the waittime is above some threshhold, send a
notification.
Set lock timeout to 0 for each connection, so that any time a block occurs,
the process will get an error 1222 and stop. You will have to add code to
retry if needed. You can then set up an alert to notify you when error 1222
occurs, or you could change the definition of error 1222 to include writing
it to the event log. Getting every session to set the lock timeout value may
require changing a lot of application code.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Rob" <rhchin@.hotmail.com> wrote in message
news:02ba01c38f5a$285b5a50$a101280a@.phx.gbl...
> Is there a way to be notified automatically when blocking
> occurs (either via net send or e-mail and maybe even have
> that written to the NT event log)?
> Thanks|||Oops, I also meant to suggest you take a look at these KB articles:
http://support.microsoft.com/default.aspx?scid=kb;en-us;271509&Product=sql2k
INF: How to Monitor SQL Server 2000 Blocking
http://support.microsoft.com/default.aspx?scid=kb;en-us;283725&Product=sql2k
INF: How to View SQL Server 2000 Blocking Data
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uOe6jK2jDHA.2964@.tk2msftngp13.phx.gbl...
> Hi Rob
> Blocking happens all the time, but it is usually for so short a period of
> time that if you had a notification every time you thing there was another
> spam virus. There is no automatic way to e notified about blocking, but
here
> are some avenues you might consider:
> Set up a script to run a loop, that captures sysprocesses output and saves
> it in a table. Compare the waittime column from one run to the next, if
the
> blocked column is >0. If the waittime is above some threshhold, send a
> notification.
> Set lock timeout to 0 for each connection, so that any time a block
occurs,
> the process will get an error 1222 and stop. You will have to add code to
> retry if needed. You can then set up an alert to notify you when error
1222
> occurs, or you could change the definition of error 1222 to include
writing
> it to the event log. Getting every session to set the lock timeout value
may
> require changing a lot of application code.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Rob" <rhchin@.hotmail.com> wrote in message
> news:02ba01c38f5a$285b5a50$a101280a@.phx.gbl...
> > Is there a way to be notified automatically when blocking
> > occurs (either via net send or e-mail and maybe even have
> > that written to the NT event log)?
> >
> > Thanks
>

MOM blocking analysis

MOM contains its own Block Analysis script. It is a script written on
VB, that looks for the monitored servers, creates for each one
MomCreateObject("SQLDMO.SQLServer"), afterwards connects to each
database on each server and executes SELECT GETDATE() query. If MOM
doesn't receive answer for 6 minutes, it sends alert. Several times
since I started to monitor my servers I received the next alert:

The program "SQLDMO_789" has been blocked for 6 minutes on database
BurstingDataWarehouse in the SQL instance MSSQLSERVER. The defined
acceptable blocking threshold is 1 minute(s). "SQLDMO_789" is running
on SPID 134 as login NT AUTHORITY\SYSTEM and is blocked by SPID 133.
The resource id is KEY: 10:2:1 (a2007950f190)

SQLDMO_789 - is the MOM itself (number varies from time to time). 10 -
is BurstingDataWarehouse database. As far as I can judge, MOM connects
to the server succesfully (otherwise, how can it know SPID?) The server
itself worked fine at that time - nothing unusual, all the jobs
finished succesfully including the heavy ones. What can block SELECT
GETDATE() query for 6 minutes?I had a similar issue and it turned out that some scrappy application
held thousands of locks on the tempdb. Run sp_who2 in combination with
sp_lock to see which process is blocking the MOM agent.

M