Viewing 15 posts - 6,136 through 6,150 (of 22,219 total)
You'll also see the predicates used against the indexes come from the ON clause or the HAVING clause in queries. Don't be surprised if it's not just your WHERE 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
May 9, 2015 at 2:48 am
xsevensinzx (5/8/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
May 8, 2015 at 9:18 am
All good choices. Another way would be to capture extended events (or trace) for all insert/update/delete commands against the table. It won't show rows affected, but you can tell what...
"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
May 8, 2015 at 8:32 am
That's not really ad hoc or dynamic SQL. The query is going to be the same every time you run it. You're not building it on the fly. You just...
"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
May 8, 2015 at 8:31 am
xsevensinzx (5/8/2015)
GilaMonster (5/8/2015)
xsevensinzx (5/8/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
May 8, 2015 at 6:48 am
The execution plan doesn't seem to have made it. Plus, posting a picture of an execution plan is not posting an execution plan. The important parts of an execution plan...
"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
May 8, 2015 at 6:42 am
xsevensinzx (5/8/2015)
spaghettidba (5/7/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
May 8, 2015 at 6:36 am
Based on just general outline, it's hard to make substantial suggestions.
At it's core, a deadlock is about performance. If a transaction completes extremely fast, the chances of it causing 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
May 8, 2015 at 6:17 am
Capture the execution plan for the query. I'd also capture the plans for the individual views.
Combining views, even through something as seemingly innocuous as a UNION ALL, is a...
"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
May 8, 2015 at 4:55 am
Sean Lange (5/7/2015)
GG_BI_GG (5/7/2015)
Ok. I will look..But is there any option for a subqeury (COALESCE), CROSS APPLY...
COALESCE is just another function and is not at all relevant here. Not sure...
"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
May 7, 2015 at 4:25 pm
Functions against columns lead to scans. Period. End of story. You can't have the functions there AND get good performance. No matter what.
Also, DISTINCT is an aggregation function suggesting that...
"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
May 7, 2015 at 1:05 pm
GilaMonster (5/7/2015)
Ok, I need to write something.Article requests?
I'll write one and then you can correct 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
May 7, 2015 at 1:01 pm
That's part of the object level permission as defined on the database you're scripting. You could probably write a PowerShell routine to remove it later.
"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
May 7, 2015 at 12:56 pm
If you're using the Wizard, when you get to Set Scripting Options, click on the Advanced button. There's a "Script Object Permissions" check box. Make sure that's disabled. That should...
"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
May 7, 2015 at 10:00 am
If you're really serious about learning SQL Server, first, assuming you don't have an MSDN subscription where you can just download a copy of SQL Server, you'll need to purchase...
"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
May 7, 2015 at 7:41 am
Viewing 15 posts - 6,136 through 6,150 (of 22,219 total)