Profiler is picking the wrong SQL instance

jclermont · April 17, 2011 10:59AM

I am profiling an ASP.NET web application through IIS. The application is configured to use a local instance of SQL Server 2005 Standard. The instance name is SQLSTD.

When I profile the application and enable SQL profiling, it never collects SQL data and complains about SQLEXPRESS. I do have SQL 2008 express and 2008 R2 express installed as well. Maybe this is confusing it?

I also confirmed that the trace provider is enabled for my SQLSTD instance by running 'logman query provider' and seeing a line for SQLSTD Trace.

Note: SQL 2005 Standard was installed *after* ANTS Profiler. Maybe that's the issue?

I need some help. Thanks.

Brian Donahue · April 18, 2011 4:13AM

It's probably nothing to do with SQLEXPRESS and more to do with trace not being configured correctly. The Profiler tries to be "helpful" and misidentifies the issue as being related to SQL Express if it finds an instance of SQL Express on the server.

Please see this article.
http://www.red-gate.com/supportcenter/C ... 000480.htm

jclermont · April 18, 2011 8:16AM

When I check the registry key in the article, it says SQLEXPRESS only.

I definitely have SQL Standard 2005 installed as well, though it's not showing in this registry key.

What do you suggest?

Brian Donahue · April 18, 2011 9:10AM

Sounds like a SQL Server installation issue. Not my forte. Let me see what I can find out.

Brian Donahue · April 18, 2011 9:50AM

Not sure what's going on but the server needs to be named in that key or else Perf Profiler will not set up a trace session for it. Maybe you could just stick it in there using Regedit?

jclermont · April 20, 2011 8:21AM

That did the trick! Thank you very much. Such a powerful tool.

Profiler is picking the wrong SQL instance

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk