I am just looking around trying to figure out good practices for
troubleshooting SQL Server 2008.
Trying to be ProActive instead of ReActive. What I am trying to do is build
a quick emergency plan to watch my database in case of troubles. Something I
can setup and when trouble happens I can execute and start figuring out what
has caused the problem. Like deadlocks, contentions etc..... Just asking
around for advice and what other DBAs are doing. I know this is very broad,
but someone might know something I total didn't know existed.
Thank You.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-performance/200908/1
http://www.SQLBenchmarkPro.com
SQLBenchmarkPro monitors SQL 2000 / 2005 & 2008 from a single installation
It is also the most light-weight server impact wise & fastest / most
accurate in trace file parsing / consumption
Cheers,
Greg Linwood
"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote in message
news:9ad8fe2c9500f@uwe...
"Hoardling1 via SQLMonster.com" <u43783@uwe> wrote in message
news:9ad8fe2c9500f@uwe...
Greg Linwood wrote:
>Our product SQLBenchmarkPro is purpose built to do exactly what you're
>referring to:
>
>http://www.SQLBenchmarkPro.com
>
>SQLBenchmarkPro monitors SQL 2000 / 2005 & 2008 from a single installation
>
>It is also the most light-weight server impact wise & fastest / most
>accurate in trace file parsing / consumption
>
>Cheers,
>Greg Linwood
>
>> Anyone have any projects/solutions or SQL Profiler setups for
>> troubleshooting.
>[quoted text clipped - 13 lines]
Uri Dimant wrote:
>Check it out
>- SQL Server 2008 Diagnostic Information Queries
>-- Glenn Berry
>-- May 2009
>-- http://glennberrysqlperformance.spaces.live.com/
>
>> Anyone have any projects/solutions or SQL Profiler setups for
>> troubleshooting.
>[quoted text clipped - 13 lines]
>>