Viewing 15 posts - 1,006 through 1,020 (of 22,219 total)
We had a directive from corporate to upgrade all our server OSes to 2019. I was informed by IT that they were going to in-place upgrade the 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
February 2, 2022 at 7:31 pm
PostgreSQL also sort of, but sort of doesn't, require semi-colon's.
"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
February 2, 2022 at 5:04 pm
Logins are not really a thing in Azure. I mean, they are, but they're not. It's down to users at the database level. It's key to always think of 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
February 2, 2022 at 3:26 pm
You could use the compare utility within SSDT to move only parts of a deployment. Automating that is likely to be somewhat difficult.
"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
February 2, 2022 at 3:17 pm
Lat & long are numbers, not characters. Transaction sequence, almost definitely a number. Wow.
"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
February 2, 2022 at 3:14 pm
I'm not sure what my point really was, but I guess it wasn't really arguing about where to put the semicolon. My issue is more with the lack 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
February 2, 2022 at 3:12 pm
If you're exploring if stats are the problem, no, I wouldn't update first. Instead, look to the execution plans and see what the estimated number of rows is. Then, look...
"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
February 1, 2022 at 2:57 pm
Additionally, remember that unique indexes drive choices by the optimizer but may never end up in sys.dm_db_index_usage_stats, so be extra cautious about using that as a reference for which indexes...
"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
February 1, 2022 at 2:34 pm
For the love of Codd, store numbers in a number defined column and strings in string defined columns. Anything else is begging for trouble.
In this case, CAST is 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
February 1, 2022 at 2:15 pm
Yeah, it's the "why" really, for the most part.
Look, code any way you want to. It's not my place to dictate or declare anyone wrong, or evil or anything like...
"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 31, 2022 at 9:53 pm
Hey all, a bit rushed this AM. Thanks for all the feedback. Appreciate.
And yeah, fully teaching the why's & how-fors & 'causes around stuff like SELECT * or ;WITH or...
"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 31, 2022 at 2:16 pm
But isn't a semi colon required I the CTE is in a stored procedure?
100%. Absolutely. The semi colon is a statement terminator. Meaning, the previous statement has to 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
January 31, 2022 at 2:13 pm
So, you're jamming that semi-colon, which is a statement TERMINATOR, at the front of your WITH clause. Are you doing that on the second query? That could be the issue....
"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 28, 2022 at 1:39 pm
And, you're hopping a pretty big gap, the cardinality estimation engine change that occurred in 2014. You need to plan for that just as you worry about the exact versions...
"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 28, 2022 at 1:36 pm
You can't create a view from a stored procedure.
Why do you need to create a view from a proc? A view is something that should be created and left 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
January 27, 2022 at 12:33 pm
Viewing 15 posts - 1,006 through 1,020 (of 22,219 total)