Viewing 15 posts - 4,576 through 4,590 (of 22,219 total)
koti.raavi (7/21/2016)
Thanks for your response; you mean to say if query is big it’s better to use CTE instead of derived table?
Grant Fritchey:
Thanks for your response.
1) I know...
"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 21, 2016 at 4:11 am
GilaMonster (7/21/2016)
Hugo Kornelis (7/21/2016)
But frankly, I don't think I know anyone that would fit the bill on these.
I've done the second a few times, out of forgetfulness only not malicious...
"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 21, 2016 at 4:07 am
BrainDonor (7/21/2016)
Does anybody know who the "Hotshot SQL Guru" is?https://tmblr.co/Z14uHt29WaOS7
https://tmblr.co/Z14uHt29Ww0kS
https://tmblr.co/Z14uHt29ZP3zF
Somebody wasn't impressed.
Innocent of that crime... yikes.
"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 21, 2016 at 4:05 am
Even for a data warehouse you don't want to move all the rows every time. You have limited to zero tuning opportunities for a query without any filtering.
"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 21, 2016 at 4:04 am
It's about capturing metrics. If you suspect that an action on the app is delayed by other actions on the database, you'd focus on queries against the database during the...
"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 20, 2016 at 9:36 am
matt.gyton (7/20/2016)
Many thanks for all your responses. I have restored a fresh copy of the database to try and ensure there are no differences and all these things appear...
"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 20, 2016 at 6:24 am
koti.raavi (7/20/2016)
1)
If table variable is storing in tempdb why can't I use them like temp tables?. How can I check table variable in tempdb?.when...
"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 20, 2016 at 6:01 am
The scans and the hash matches make sense. You don't have any kind of a WHERE clause to filter the data so the query is returning 300,000 rows. Scans &...
"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 20, 2016 at 5:55 am
If you're getting problematic plans, it's probably because of out of date statistics, so getting more up to date statistics is usually the solution. USE PLAN might not work 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
July 20, 2016 at 5:36 am
Doctor Who 2 (7/19/2016)
Tonight I have a chance to go through the MSDN article you've posted in response to my question. It looks as though I need to first...
"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 19, 2016 at 8:23 pm
Jeff Moden (7/19/2016)
And stats. Small change in stats can make for wildly different executions.
Absolutely!
Also, plans can look the same but still be very different on the inside, estimated versus...
"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 19, 2016 at 4:14 pm
And then check for compression on the one with fewer reads.
"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 19, 2016 at 12:26 pm
Upwards compatibility is never guaranteed. This is because new functionality is introduced that older software can't cope with.
"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 19, 2016 at 6:07 am
You just have to set up your network so that the server is visible within it, then you're off to the races.
"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 19, 2016 at 6:05 am
Rod at work (7/18/2016)
Grant Fritchey (7/18/2016)
"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 18, 2016 at 11:37 am
Viewing 15 posts - 4,576 through 4,590 (of 22,219 total)