Viewing 15 posts - 3,451 through 3,465 (of 22,219 total)
Sometimes, not always, an OR causing slow behavior can be replaced by two copies of the query combined using UNION ALL. Not seeing the details here I don't want 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 14, 2017 at 5:02 am
The reason for something like this is the queries being sent to your system. You need to capture those queries. I'd suggest one of two approaches. First, the most accurate,...
"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, 2017 at 5:01 am
I agree with everything Alan said. I would test both. It sounds like a filtered index is likely to work better for you, but test both to be sure. Just...
"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, 2017 at 4:56 am
Resource DB is a little different. Here's an article on it.
"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 13, 2017 at 8:24 am
I pointed you to this bit of documentation once before. I'd suggest reading all through it. It's going to help you quite a bit with Azure SQL Database.
"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 13, 2017 at 8:21 am
A GIANT pinch of salt. The missing index DMVs do not relate the suggested indexes back to queries in any way. You may have a suggestion for an index for...
"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 13, 2017 at 2:24 am
The driver has to be the leading edge and then subsequent columns. Also look for ones that are unique and non-unique but have the same columns. Always go for keeping...
"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 13, 2017 at 2:20 am
Exec plans at least to try to answer this.
"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 13, 2017 at 2:16 am
DimPerson - Wednesday, December 13, 2017 1:38 AM... the default is 1000 pages as this "based on Microsoft's recommendations" ....
Or, more accurately,...
"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 13, 2017 at 2:11 am
Hi Sir, Thanks for the response. One followup question, if I not able 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 13, 2017 at 1:45 am
Brandie Tarvin - Tuesday, December 12, 2017 6:27 AMSmooth, Grant. Very smooth!I applaud how you slid that in there.
Thanks. Just trying 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 12, 2017 at 6:37 am
That's not available in Azure SQL Database because you're not dealing with a server, which uses default trace to generate the report. Instead you're dealing with a database as a...
"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 12, 2017 at 6:22 am
Intellisense works fine as long as you only ever use SQL Prompt.
"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 12, 2017 at 6:19 am
You can run Extended Events to capture this type of behavior. If you want to schedule a script to run, you can do that through Azure Automation.
"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 11, 2017 at 6:35 am
You can't change that setting in Azure SQL Database currently. You can use Database Scoped Configuration to control the MAXDOP, but I'm not a fan of this approach.
"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 11, 2017 at 6:34 am
Viewing 15 posts - 3,451 through 3,465 (of 22,219 total)