June 18, 2009 at 5:47 pm
How can you find the worst performing queries in sql 2000?
It seems like a bit of a mission because you don't have access to the dmvs like in 2005.
June 18, 2009 at 5:56 pm
You have the profiler traces and execution plan but I always used profiler, it is best to run it in a test because it takes a lot of resources.
Kind regards,
Gift Peddie
June 19, 2009 at 3:24 am
Server-side trace. Far less impact than profiler and you can schedule it with SQL Agent.
There's a section on creating a server side trace here - http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 23, 2009 at 6:40 pm
thanks Gail- that was quite informative.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy