Search
InstantDoc ID
GO

Browse By: Author | Issue

November 23, 2004 09:23 PM

Running Profiler on a Busy Server

Rating: (0)
Brian Moran
SQL Server Magazine
InstantDoc ID #44306

I tried to use SQL Server Profiler to tune a busy SQL Server database for one of my customers. The 8GB database was running on an 8-CPU server running at 70 percent to 80 percent CPU utilization. The server promptly became nonresponsive, and I had to restart the server. Microsoft Developer Network (MSDN) support told me that Profiler can place a heavy burden on busy SQL Servers. To tune the database, I need the SQL text and reads that the queries generate. How do I gather this information from a busy, multiprocessor SQL Server without running the server into the ground?

...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Compare Member Benefits

Add a Comment

Nice idea to have the maximum size as a method to kill the trace. I did some creating a timed rpofiling of a heavy SQL server, which was writing files of 200 MB, but then moving on to the next file. End up with some BIG files (1.6 GB for a 10 minute time slice), but eventually, after loading it all into a seperate table we got some interesting results. BTW - if you need to reduce size, I found the trace files compress VERY well! A lot better than moving large files around your network :-)

Regan12/6/2004 8:24:43 AM

You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS

© 2010 Penton Media, Inc.

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.