Viewing 15 posts - 5,296 through 5,310 (of 22,227 total)
Steve Jones - SSC Editor (12/16/2015)
Jeff Moden (12/16/2015)
Family always comes first but that's a bugger. Was looking forward to seeing you again, ol' friend.
Ditto. Was hoping to get there,...
"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
December 16, 2015 at 8:26 am
shirish_padekar (12/16/2015)
"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
December 16, 2015 at 4:12 am
The trick is going to be identifying what is causing the so much CPU to be used. Since you're just getting started and you're on 2008, the best approach is...
"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
December 16, 2015 at 4:07 am
A simple way? None that I'm aware of.
I did a search. The script documented here comes up pretty frequently, but it's anything but simple.
Looking at Paul's script, I'm pretty sure...
"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
December 15, 2015 at 6:57 pm
What are the actual wait metrics? Check sys.dm_os_wait_stats before, during, and after the issue. Also, look to sys.dm_exec_requests while the issue is running to see active waits. You need to...
"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
December 15, 2015 at 6:53 pm
sql.queries (12/15/2015)
I think I will need to study execution plans to accomplish this. Any advice where to start?Thanks
Actually, yes. Look down to the links in my signature
|
|
V
"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
December 15, 2015 at 7:21 am
GilaMonster (12/15/2015)
Don't just look at the execution plan operators and assume which is better. Test. Get actual metrics and compare numbers (and I don't mean cost %).
THIS!
Scans are not necessarily...
"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
December 15, 2015 at 3:14 am
xsevensinzx (12/14/2015)
Why prove the usefulness of R to the DBA as opposed to a general purpose language like Python that can accomplish the same thing?...
"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
December 15, 2015 at 3:07 am
It's down to disks and controllers. If you're separating storage onto multiple physical locations (and I use that word because if you're on a SAN, using LUNs, and those are...
"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
December 14, 2015 at 11:48 am
Dougieson (12/14/2015)
So, if we can safely assume you are using SQL Server 2014 (cause you...
"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
December 14, 2015 at 9:07 am
I do feel for the person. They seem so desperately over their head and quite ill-equipped to deal with that fact, let alone all the other crap that's coming their...
"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
December 14, 2015 at 7:28 am
1) Yeah, possibly. Hard to say without seeing the execution plan and wait statistics. I'd for sure collect those to understand what's happening here.
2) No, the COUNT(*) is a fine...
"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
December 14, 2015 at 7:25 am
Check the error logs on the primary and the secondary to see what the issue is. Look to the wait statistics on both to understand if it's just a simple...
"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
December 14, 2015 at 7:12 am
I'm with Perry. AG is superior in every possible way except the licensing costs.
"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
December 14, 2015 at 7:10 am
shamshad.ali (12/14/2015)
Sorry for asking this, as I wanted to get the idea from those who used...
"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
December 14, 2015 at 7:09 am
Viewing 15 posts - 5,296 through 5,310 (of 22,227 total)