Viewing 15 posts - 3,466 through 3,480 (of 22,227 total)
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
Generally you just write the delete script for the children and then for the parent. there's no magic here.
"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:28 am
It's all about understanding what you're doing well enough to educate people. If they have a query that is SELECT * FROM Table and it returns 20 terabytes of 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
December 8, 2017 at 6:40 am
Instead of using an IN clause, use another JOIN to retrieve that data. You would have to build a dynamic statement to perform a count before you tried to JOIN,...
"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 8, 2017 at 6:33 am
It's always tough to make any kind of recommendation on stuff like this. Every situation has unique aspects that my affect what you do and how you do it. However,...
"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 8, 2017 at 6:23 am
"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 6, 2017 at 10:38 am
If you've done a rebuild, it shouldn't be fragmented any more. What command are you using to do that rebuild?
"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 4, 2017 at 2:10 pm
Are you rebuilding the index? A rebuild should result in reduced fragmentation.
BTW, if you're not experiencing lots of scans, it's possible that you don't need to worry 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
December 4, 2017 at 12:39 pm
Viewing 15 posts - 3,466 through 3,480 (of 22,227 total)