Viewing 15 posts - 1,351 through 1,365 (of 22,219 total)
This one is all about opinion, so, take with a grain of salt the size of a house.
You're being a little bit paranoid. SQL Server is one of the most...
"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
April 22, 2021 at 11:19 am
Agreement with what everyone else added.
"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
April 21, 2021 at 6:12 pm
Heh... I agree with Grant on logical execution being left to right and data flow being right to left and both being top to bottom (except on super-umbra-red...
"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
April 21, 2021 at 6:11 pm
Thank you Grant, actually if you have the power you can just delete that, I didn't redact parts of the screenshot I should have. Reporting it was 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
April 21, 2021 at 6:09 pm
I'm a little confused. You keep talking about servers and server specs. However, you also said you were using Azure SQL Database. That doesn't involve servers. So... which is 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
April 21, 2021 at 11:03 am
OK. This is a fun one.
Execution plans are logically executed from left to right, and roughly, top to bottom. You can validate I'm right about this by looking at 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
April 21, 2021 at 11:00 am
Yep. Without the rest of the error message, I can't even hazard a guess. Jeff is probably right (says Grant all 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
April 21, 2021 at 10:46 am
Ha! Clearly I type slowly and/or too much. Agreement with @Ant-Green. +1
"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
April 21, 2021 at 10:44 am
You're in a bit of a tough spot, not having a network. However, probably, your best bet would be to use Azure SQL Database (or AWS RDS 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
April 21, 2021 at 10:42 am
All the votes for Johan's solution with Extended Events. #TeamXE
Also, I unspammed TangoVictor's first post, not noticing the second. Not sure why that happened. I put it back to spam...
"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
April 21, 2021 at 10:34 am
For the restore operation, according to the documentation, you can go as far back as a 2005 backup and restore it to 2019. As to the in-place server upgrades,...
"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
April 21, 2021 at 10:32 am
The only negative to any approach is when it's either destructive of your data, or doesn't work well. If, in your testing, dropping and recreating the indexes works better, then...
"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
April 19, 2021 at 2:46 pm
You could encrypt it with a password. You can use the Data Protection API (DPAPI). Here's an article on it. Another showing how to create a password protected...
"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
April 19, 2021 at 11:50 am
Auto close is a pain. Happy you fixed 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
April 19, 2021 at 11:44 am
Hey all!
Thanks for the feedback. I have no arguments to make against any of it. As I said in the editorial, all I have are questions here.
One point I will...
"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
April 19, 2021 at 11:20 am
Viewing 15 posts - 1,351 through 1,365 (of 22,219 total)