Viewing 15 posts - 5,671 through 5,685 (of 22,219 total)
lgluna20 (8/21/2015)
Thanks you very much for your answer
Sorry in case of the questions number 3 I was not clear about it.
Basically as you know SQL Server include Maintenance...
"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
August 22, 2015 at 4:35 am
Please don't cross post questions. It just confuses the conversation.
Please post responses to this question over here.
"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
August 21, 2015 at 12:32 pm
You're basically doing the same thing as a side-by-side upgrade. That's a very straight forward mechanism. Lots of documentation out there on it. You have options and it depends 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
August 21, 2015 at 12:27 pm
What it does is acts as a marker for if a given row has been updated. So you can read the data, get the current rowversion, then when you go...
"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
August 21, 2015 at 12:18 pm
Eric M Russell (8/21/2015)
However, the MERGE statement is complicated enough that it could use a GUI...
"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
August 21, 2015 at 8:49 am
If you want to help out, here's the thread.
"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
August 21, 2015 at 7:15 am
lgluna20 (8/21/2015)
Thanks for your kind support and answerI want to know
1-Is it necessary to execute update static and rebuild index daily ?
It really depends on your system. 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
August 21, 2015 at 6:52 am
THREADIZENS!
Your knowledge is needed. I've got an idea for an article. It's meant to be a basics article for introductory level people. I want to put together that standard 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
August 21, 2015 at 6:39 am
It's filtering 14 days here:
WHERE exec_date >= dateadd( day, -14, getdate() )
So, change the -14 to -1 and you're pretty much finished if everything else is working for you.
I don't...
"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
August 20, 2015 at 12:15 pm
But you can create a nonclustered columnstore with a row-based clustered 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
August 20, 2015 at 10:59 am
I'd still run a consistency check.
"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
August 20, 2015 at 3:02 am
Rebuilding an index updates the statistics at the same time. So the order in which you run these things does matter. Understand that if an index is not rebuilt, 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
August 20, 2015 at 2:53 am
After reading through all this excellent advice, the only thing I'd add is a question. Do you really need DISTINCT? That's adding quite a lot of overhead on top 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
August 20, 2015 at 2:50 am
I like what Jason did. As soon as you start seeing correlated sub-queries like that, usually the best approach is either a JOIN or an APPLY.
"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
August 20, 2015 at 2:39 am
Sean Lange (8/19/2015)
"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
August 19, 2015 at 9:44 am
Viewing 15 posts - 5,671 through 5,685 (of 22,219 total)