Viewing 15 posts - 3,991 through 4,005 (of 22,224 total)
Your only hope is that the application name is supplied with the connection. It's optional, so you may not see it. I'd strongly suggest, as has everyone else, cleaning up...
"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
I'd suggest setting up trace events to capture remote procedure calls and sql batch. You should be able to identify the login from there. The application name might not 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
You mean the extended events for Idera are missing? Not sure. You might want to see if Idera has a forum or some means of asking this question.
"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
Since you can't go to 2016 and take advantage of Query Store, upgrading to 2014, you need to, as much as possible, simulate having Query Store available. With that in...
"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
Excellent article.
I would suggest a single caveat that having a secondary copy of the data somewhere other than Azure is a good practice if this is business critical...
"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
It's not always about free consulting. When we had people get past our tier 1 phone interview, assuming they did well during our second discussion (white board & all that...
"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
"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
Interesting. I've never seen that approach before. I'm not sure I'm crazy about it at all. In general I wouldn't really bother counting, or worrying about the count, of CXPACKETS....
"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
I'm not sure where you got the concept of balancing CXPACKET and SOS_SCHEDULER_YIELD. That's not a valid approach that I've ever heard of.
CXPACKETS just indicates that parallelism 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
However, I'm a little hung on why this is so vitally important? What's the end goal? What are we trying to do? Is it just about learning index internals?
"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