December 19, 2007 at 9:35 am
I'm trying to track down a bottleneck thats causing our windows application to hang or slow down to a crawl and want to set a trace from sql. In researching this I found the following command that starts the trace however the ctrl.guid.all file is not found. I've also tried using the ctrl.guid.adonet file reference since we are using .NET but that too is not found.
@Logman start MyTrace -pf ctrl.guid.all -ct perf -o Out.etl -ets
I may be missing something regarding this file and either creating it or downloading it. I do see a list of providers when I invoke the [logman query providers] command so I'm thinking that this file either exist with some other name or needs to be created. Any ideas regarding this or other tracing methods to try are greatly appreciated.
December 19, 2007 at 9:47 am
Okay, I have found the control guid files. In the MS doc http://technet.microsoft.com/en-us/library/aa964124.aspx there is a link Data_Access_Tracing.exe sample code that gives you all the files. Now I'll try to make this thing work.
December 19, 2007 at 9:52 am
Use SQL Profiler
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
December 19, 2007 at 1:33 pm
Ahh, thanks, this does look like a better tool.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply