January 7, 2009 at 2:25 pm
Hi folks,
I am running a trace and adding the perf mon result in order to track down some memory:page/sec spikes. When I run the perf mon by itself I get many spikes close together.
When I create a counter log and capture the memory:page/sec. followed by combining it with my profiler trace in order to find the SP or SQL statment that is causing it the line I get a graph looks much much wider and basically looks nothing like the system monitor did viewing it through the GUI.
any suggestions.
Thanks
January 7, 2009 at 6:16 pm
What is the time period that you are looking at in Profiler with the perf data loaded? If you restrict the Perfmon graph to the same period of time in the properties, does it look the same then?
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
January 8, 2009 at 7:44 am
I am doing a few things.
I first open the perf mon and watch the graph in real time.
Then during that same time period I run profiler and permon trace. with the hopes that my trace will look like what I saw when I watched the graph in real time.
I am running the trace for about 2-3 min nothing large
Thanks
January 8, 2009 at 8:25 am
When you set up the counter log what was the Refresh Interval?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
January 8, 2009 at 10:40 am
found the problem, I had left the duration on 15 secs I needed to set it to 1 sec.....and then WORKS
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply