Viewing 15 posts - 3,106 through 3,120 (of 22,227 total)
And the second question, if I restore existing database, for example we 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
July 27, 2018 at 6:17 am
And the delete, while fast, is not free, so it's also adding a little to 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
July 26, 2018 at 12:41 pm
Getting exact measures is going to be very hard because, at the root, is the query run more than once with a unique data set each time, or a mixed...
"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 26, 2018 at 12:40 pm
You literally can not go wrong using Paul Randal, and his team, as a guide.
Best of luck on figuring things out. Come back here as you need...
"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 26, 2018 at 8:03 am
"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 26, 2018 at 7:43 am
If you're capturing query metrics on SQL Server 2012 or greater, instead of using trace, I strongly recommend you use Extended Events. It's much more lightweight and easier to filter. "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 26, 2018 at 7:39 am
Oh, and, you're on 2014. The system_health extended events session captures deadlocks. You don't need 1204. It's just going to dirty up your logs.
"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 26, 2018 at 7:32 am
I honestly hate trace flag discussions.
However, I'd suggest adding 2371 to the 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
July 26, 2018 at 7:31 am
Strong recommendation.
Don't use the ring buffer target. It's very attractive, but it leads to problems. Read this post by Jonathon Kehayias for details.
"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 26, 2018 at 7:30 am
One immediate concern I would raise with whoever has asked you to back up a table instead of the database. How do you restore it? You need a plan for...
"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 26, 2018 at 7:28 am
Target and Total Server Memory are frequently identical after the server has been running for a bit. SQL Server will consume the memory available and then hold on to 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
July 26, 2018 at 7:26 am
I'd monitor it using Extended Events (or if you're on 2008, Trace Events). You can capture the query. You won't see the data, but you can see the query.
"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 25, 2018 at 11:44 am
Yeah, I agree with Drew. Rather than try to capture the SELECT statement, just capture the data from the data modification through the OUTPUT clause.
"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 25, 2018 at 7:56 am
A backup and a restore followed by data cleansing would be a lot easier.
Otherwise, if you're moving subsets of data, especially since it's going to be relational data,...
"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 25, 2018 at 7:17 am
If you mean something along the lines of, within T-SQL:
SELECT * FROM LastSelectResultSet
Then the answer is no. However, if you want to see what's happening on your 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
July 25, 2018 at 4:54 am
Viewing 15 posts - 3,106 through 3,120 (of 22,227 total)