Viewing 15 posts - 9,376 through 9,390 (of 22,224 total)
zi (11/5/2013)
"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
November 5, 2013 at 2:12 pm
I'd suggest not relying too much on those screens. Instead, if you're interested in monitoring the system, use a combination of Performance Monitor, Dynamic Management Objects and Extended Events. You'll...
"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
November 5, 2013 at 9:27 am
It doesn't sound like tempdb was the issue. I'd suggest monitoring your wait statistics (sys.dm_os_wait_stats) and running an extended event session to capture query metrics.
Don't run the Profiler gui against...
"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
November 5, 2013 at 8:47 am
Use extended events to capture the data to a file.
Then, you can use fn_xe_file_target_read_file to read the file. It'll output as XML. Here's an example XML query that might be...
"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
November 4, 2013 at 12:31 pm
I'm not sure who wrote that tip, but in case it was me...
I must have meant to just clean up the code. It's actually not a major performance enhancement...
"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
November 4, 2013 at 12:24 pm
Without more details, I can't tell you what's wrong.
I'm with Gail though. Use backup and restore. Doing that will not only get you your copy of of the database, but...
"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
November 4, 2013 at 7:02 am
Ed Wagner (10/31/2013)
GilaMonster (10/31/2013)
Jeff Moden (10/31/2013)
GilaMonster (10/31/2013)
I'm unlikely to be around much during the week from now on (at...
"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
October 31, 2013 at 1:15 pm
In general, more disks can improve performance, not generally hurt it. But, you also have to have more controllers to really achieve meaningful benefits. In general, based on what you're...
"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
October 30, 2013 at 12:37 pm
Your second query, the UNION, is getting a timeout from the optimizer. That means the plan is likely to be suboptimal. I'd suggest looking at ways to simplify the query....
"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
October 30, 2013 at 12:03 pm
I meant internal memory measurements within SQL Server such as ConnectionMemory, DatabaseCacheMemory or FreeMemory. In theory you should be able to look at all the these and see what the...
"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
October 30, 2013 at 7:46 am
You should look to the execution plan to understand what is happening in your query and how the optimizer is choosing to select your data.
"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
October 30, 2013 at 7:42 am
Lots of NOLOCK in there. That's scary.
One thing you can do that will immediately help performance, whether you keep the recompile in place or not. The IF statement puts the...
"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
October 30, 2013 at 7:33 am
Right with you til #5 Kevin. NEVER use ALWAYS and ALWAYS avoid NEVER. 😛
"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
October 30, 2013 at 6:31 am
Not seeing the query, I can't say what's going on, but, on a guess, you're probably seeing some sort of bad parameter sniffing issue where the plan you generated after...
"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
October 30, 2013 at 6:28 am
Total Memory is the amount that SQL Server has allocated. Your average server will allocate as much memory as it can and then keep it. So this counter will generally...
"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
October 30, 2013 at 6:25 am
Viewing 15 posts - 9,376 through 9,390 (of 22,224 total)