September 3, 2003 at 1:47 am
You could start by setting up a few traces. Take a look at "Monitoring with SQL Profiler" in Books Online.
Also, if you setup the the trace to run on the server without using SQL Profiler you'll reduce some of the overhead created by running the trace. Have a look at sp_trace_create in Books Online
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface ![]()
--------------------
Colt 45 - the original point and click interface ![]()
September 3, 2003 at 11:03 am
I had the server guys run a trace for me but they don't which counters they should be monitoring ? Which counters should I monitor ?
September 3, 2003 at 12:28 pm
Use one of the built-in templates traces with Profiler. If your application is built using mostly stored procedures, use the "SQLProfilerTSQL_SPs" template. Click on the Data Columns and add "Duration" as an output. Click on Filters, drill to "Duration" --> "Greater than or equal to" and then type 3000 (for 3 seconds.)
Name your trace, pick a table to log the trace to, and click "Run"...
--
When you've collected some data, let us know, and we can supply a couple scripts that will enable you to do some analysis...
--
HTH,
Jay
Edited by - jpipes on 09/03/2003 12:27:55 PM
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply