Viewing 15 posts - 3,091 through 3,105 (of 22,219 total)
Ok, Grant. Let me make sure I understand what you're suggesting...
"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
July 31, 2018 at 7:44 am
It's technically unsupported, but you could use sp_msforeachtable to walk through and do what you want. Here's a link with examples.
"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
July 31, 2018 at 6:17 am
Our dev team is using Entity framework and now all the DB calls 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
July 31, 2018 at 6:10 am
Also, if you're doing restores of the databases to non-production environments, you can offload the logical consistency checks to those databases. You then can just do the physical_only checks on...
"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
July 31, 2018 at 5:58 am
I have a typical DWH scenario of Source --> Destination ETL.
During this ETL, 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
July 30, 2018 at 8:08 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
July 30, 2018 at 6:43 am
I've got several blog posts on the cost threshold for parallelism. First, we need to make sure you're on the service packs and CUs from the fall (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
July 27, 2018 at 5:51 pm
And the second question, if I restore existing database, for example we have...
"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
July 27, 2018 at 6:17 am
And the delete, while fast, is not free, so it's also adding a little to the time.
"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
July 26, 2018 at 12:41 pm
Getting exact measures is going to be very hard because, at the root, is the query run more than once with a unique data set each time, or a mixed...
"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
July 26, 2018 at 12:40 pm
You literally can not go wrong using Paul Randal, and his team, as a guide.
Best of luck on figuring things out. Come back here as you need...
"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
July 26, 2018 at 8:03 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
July 26, 2018 at 7:43 am
If you're capturing query metrics on SQL Server 2012 or greater, instead of using trace, I strongly recommend you use Extended Events. It's much more lightweight and easier to filter. "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 26, 2018 at 7:39 am
Oh, and, you're on 2014. The system_health extended events session captures deadlocks. You don't need 1204. It's just going to dirty up your logs.
"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
July 26, 2018 at 7:32 am
I honestly hate trace flag discussions.
However, I'd suggest adding 2371 to the list.
"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
July 26, 2018 at 7:31 am
Viewing 15 posts - 3,091 through 3,105 (of 22,219 total)