Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Third party software

Author  Topic 

ferrethouse
Constraint Violating Yak Guru

352 Posts

Posted - 2009-12-25 : 01:07:23
I've been looking at some third party software to deal with deadlocks and optimization and monitoring in general. I won't post their names here (some forums are sensitive about that) but there seems to be 3 or 4 main players. I'm just wondering what some of the established DBAs feel about these tools and if they are just fancy graphical versions of many of the stored procs and reports you can easily produce yourself inside SQL Server? I'm new to the DBA game and don't know if they are considered superfluous or a necessity.

Thanks.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-12-25 : 11:37:06
I guess it depends on how many servers you support. We have hundreds, so we have to use monitoring tools that send out alerts (emails and pages). We can't possibly monitor them manually each day. We use Microsoft's MOM to monitor our database servers.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

ferrethouse
Constraint Violating Yak Guru

352 Posts

Posted - 2009-12-25 : 12:40:19
I just have one. But I need a better way to isolate and deal with deadlocks. Our clients have been complaining about performance periodically. I can't leave the profiler running because the dashboard takes 50 seconds to load when the profiler is running and only 2 seconds when it is not running.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-12-25 : 13:12:22
To deal with deadlocks, enable the deadlock trace flag via DBCC TRACE(1222,-1). That is only good for the current SQL Server process, so in order for it to work after the restart you need to add the 1222 trace flag to the startup parameter.

It sounds like you are tracing too much information or don't have your trace configured for performance. See my blog for more information: http://weblogs.sqlteam.com/tarad/archive/2008/08/06/SQL-Profiler-best-practices.aspx

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page
   

- Advertisement -