September 4, 2008 at 1:20 am
Hi,
I have a problem with the profiler on one of our SQL-servers, the system becomes unresponsive to external queries when trying to run it.
System details, win 2003 Srv Enterprise 64 bit, SQL 2005 Ent 64 bit running on a proliant DL580G5 with 64Gb RAM and 4 quadcore processors.
The cpu load decreases from normal 10-15% to around nothing when the profiler is started. we've tried to 'lighten up' the logging so we only log a few actions on the server, still the problem persists. When running profiler on a server running 32bit applications and _a lot_ less system resources, it works fine.
I haven't found anything around problems with profiler on 64bit platforms so I'd need suggestions for where to start looking 🙂
Thanks in advance,
Micke
September 4, 2008 at 2:19 am
Rather don't run the profiler GUI on the server. That's one of the highest-impact ways to run profiler. If the server is busy, or you're tracing frequent events, rather use the server-side trace functionality.
You can use profiler to generate the script for the trace, then make the required modifications to the script (a file name) ensure that the trace will be written to a fast drive, and run the script to start the trace.
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
September 4, 2008 at 5:51 am
Gail's 100% correct.
I've got some 64 bit servers and I haven't seen this behavior, so I don't think it's the 64 bit alone that's causing the issue. Are there any other variables that you're aware of? Have you watched memory, paging... I'm not sure what else, on the server when you hit these issues?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply