Viewing 15 posts - 2,191 through 2,205 (of 22,219 total)
I hear you. Thinking about it some more, while a bit of a pain, I don't see any way this is dangerous. Sure, you have a few more files, so...
"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
January 7, 2020 at 2:48 pm
It's estimating 1.9 million rows and moving 500k. That's my first concern, not the spool. The spool is in place so that it doesn't have to do that scan over...
"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
January 7, 2020 at 2:36 pm
The better you get at communication, the better an employee you'll be. The better you get at communication, the more likely you'll get hired. Yes, if you communicate a ton,...
"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
January 7, 2020 at 2:11 pm
Honestly, testing and experience is going to be the answer. Does it sound like a reasonable approach to me? Yes.
"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
January 7, 2020 at 1:50 pm
Did you also post this question on Quora? It sounds like one I answered over there. My answer here would be largely the same.
As to a way to dip your...
"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
January 6, 2020 at 1:57 pm
Side note:
You know the missing index DMVs are just suggestions, right?
Further, there is no correlation between the missing index information and queries. Therefore, you can't know if the missing index...
"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
January 6, 2020 at 1:53 pm
Yes. The exact same queries you use to look at missing indexes in the boxed SQL Server product. Under the covers, Azure SQL Database is just SQL Server. If ever...
"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
January 6, 2020 at 1:49 pm
Yeah it's not the compression. That's fine. (although I know where you can get even better than native compression <cough> Redgate </cough>), it's the TDE with compression that can lead...
"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
January 3, 2020 at 11:12 pm
Don't forget, even with a log file, if the backup process ignored SQL Server transactions, the attach could still fail.
"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
January 3, 2020 at 2:10 pm
First, you can't do this on a server where the same database already exists. You must be doing this on a new, or different, instance of SQL Server.
"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
January 3, 2020 at 10:34 am
While the results may be the same, putting the JOIN criteria and the filtering criteria into the WHERE clause is less clear. I'd always default to having the JOIN criteria...
"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
January 2, 2020 at 1:17 pm
Check the execution plans, but I'll bet the second choice there performs better.
"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
January 2, 2020 at 1:15 pm
Thanks for the link - one that I wasn't aware of and rather good for sure
Not a problem. Niko is the best. It's where I start when I 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
December 27, 2019 at 6:06 pm
Frederico, do you have any test case to support your speculations?
I (and I guess Jeff Moden too) would be particularly interested in a test script which demonstrates advantages of...
"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 27, 2019 at 11:02 am
I would still consider them good for history/audit tables as these aren't queried often - saving on space is what would really be important here, not speed of processing...
"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 25, 2019 at 12:40 pm
Viewing 15 posts - 2,191 through 2,205 (of 22,219 total)