Viewing 15 posts - 5,746 through 5,760 (of 22,219 total)
Sean Lange (8/10/2015)
mohan_padekal (8/10/2015)
Here is the Execution PlanHow about as an attachment instead? I doubt anybody is going to waste their time piecing that back together into something usable.
+100
Please, attach...
"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 10, 2015 at 7:45 am
Back to comparing the execution plans to understand where the differences occur.
"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 10, 2015 at 7:44 am
You're going to spend a lot more time trying to create this magic query for each table that will dynamically allow INSERT/UPDATE/DELETE/SELECT than it will take you to just create...
"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 10, 2015 at 5:11 am
Can you post the execution plan? On an initial read through the procedure I didn't spot any immediate issues, so it's a question of understanding how each of those actions...
"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 10, 2015 at 5:04 am
With the data stored in a denormalized fashion like that, you've really got two choices. The better option, break up the name into multiple columns. However, that's going to be...
"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 10, 2015 at 5:01 am
UserRR (8/10/2015)
I actually read that whitepaper and got that trace flag from there.
I understand some queries might degrade, but how can the query perform 15x better with no parallelism?
Understand...
"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 10, 2015 at 4:55 am
Check out Minion Reindex[/url]. That will do what you're trying to do and a whole lot more.
"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 10, 2015 at 4:48 am
I can't replicate it here. Check your SET ROWCOUNT in the properties. Maybe that's set to 11.
"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 9, 2015 at 5:46 am
RPC Completed and SQL Batch Completed should be enough. The columns you listed sound good too.
"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 9, 2015 at 5:42 am
I can't find anything specific in the documentation. The step_id value is an INT though, so that implies a limit there. However, I sure wouldn't suggest you create a job...
"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 7, 2015 at 12:05 pm
It sure sounds like something related to parameter sniffing. Possibly it's data conversions? You're showing passing a string in one and a datetime in the one with the variable. What'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
August 7, 2015 at 11:56 am
Another vote for Minion Reindex. Absolutely worth checking out for maintaining your 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
August 7, 2015 at 10:36 am
That's odd behavior. Have you looked at the execution plans for both calls, the hard coded value and the variable? I'd be curious if there was a difference. I wouldn'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 7, 2015 at 10:34 am
Without seeing the execution plans, I'm just guessing.
First guess, these are different columns with different data and different data distributions. That's likely to result in differences in behavior. Another guess,...
"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 7, 2015 at 8:57 am
Everything Eddie said is 100% correct (of course).
One concern that you should have though, if the recovery model were changed at any point, that effectively breaks the log backup chain...
"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 7, 2015 at 8:51 am
Viewing 15 posts - 5,746 through 5,760 (of 22,219 total)