Viewing 15 posts - 15,091 through 15,105 (of 22,232 total)
Bradley B (5/7/2010)
I was working with the Army on a FileNet project that had a SQL backend. All...
"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, 2010 at 7:22 am
Brandie Tarvin (5/7/2010)
On the other hand, the DELETE statements are kinda weird. I've never seen DELETEs phrased this way and I find myself thinking there...
"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, 2010 at 7:07 am
I agree this sounds like parameter sniffing.
As an experiment, you can create local variables within your procedure and then use them in the WHERE clause. You should see 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 7, 2010 at 6:59 am
While waiting on the table defs, could you try this?
FROM T_IDYou.[dbo].[HST] h
LEFT JOIN srv1.T_id.dbo.MO s
ON h.refID=s.DistributorOrd
AND s.DistributorOrderNumber is null
"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, 2010 at 6:53 am
Two things, using views is fine, but if you starting joining views against views, you can completely overwhelm the ability of the optimizer to simplify your queries to only use...
"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, 2010 at 6:52 am
You should be able to use the processes outlined here to rebuild the tempdb with a different structure. It'll work the same way as if you were moving 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, 2010 at 6:46 am
Also, if you don't want to open a new query window, but just switch the connection in the one you're on, you can click the icon that's in 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
May 7, 2010 at 6:44 am
To capture individual statements, or batch calls, you can use a server-side trace. These are set up through the Profiler utility that comes with SQL Server. The specific event you're...
"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, 2010 at 6:42 am
I love it. They're running a delete statement with a READ_UNCOMMITTED isolation level... like that'll prevent locking.
You need to get on the vendor about the issue. It's pretty clear...
"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, 2010 at 6:24 am
mike.renwick-894639 (5/7/2010)
Anyone interested in sample code of what we did, take a look here
http://www.mediafire.com/?eim2mydnjti
Disclaimered as you'd expect.
Regarding the ongoing debate about "proper" source control usage, I think...
"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, 2010 at 6:15 am
tony.turner (5/7/2010)
eric_russell 13013 (5/6/2010)
"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, 2010 at 6:09 am
Unfortunately I don't have any funny names for code.
I do have two quasi-funny phrases that are used around here, a lot, too much.
The first, is a joke, say it, everyone...
"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, 2010 at 6:07 am
Everyone turning off parallelism is ignoring the fact that some queries can benefit. I strongly recommend you explore increasing the cost threshold of parallelism before you simply switch it off....
"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, 2010 at 6:01 am
Yep. They told me that leaving parallelism turned on (0 or some number greater than 1) and adjusting the cost threshold up is the way to go. I was told...
"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 6, 2010 at 1:09 pm
Frequently, but not always, it's not that the system can't benefit from parallelism, it's that the threshold for parallelism is set to low. The default, 5 I believe, is way...
"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 6, 2010 at 12:59 pm
Viewing 15 posts - 15,091 through 15,105 (of 22,232 total)