Viewing 15 posts - 14,581 through 14,595 (of 22,219 total)
Roy Ernest (7/23/2010)
Grant Fritchey (7/23/2010)
Ray K (7/22/2010)
Uh oh, bad blood starting to break out here . . .
Nah, the guy's taking a beating for something he didn't create. I know...
"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 23, 2010 at 8:56 am
sreedhar1.m (7/23/2010)
Do not use row and table locks.
A couple of questions. How do you go about not using locks? Aren't they pretty much required by the system when it updates...
"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 23, 2010 at 4:57 am
Take a look at a function called sp_help. I think that might move you in the direction you wish to 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
July 23, 2010 at 4:48 am
prakskarry (7/22/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
July 23, 2010 at 4:22 am
WayneS (7/22/2010)
Grant Fritchey (7/22/2010)
WayneS (7/22/2010)
How does one go about creating a connect item? I think I've got about a dozen to submit on indexes.....
It's not hard. Go to connect.microsoft.com and...
"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 23, 2010 at 4:16 am
Ray K (7/22/2010)
Uh oh, bad blood starting to break out here . . .
Nah, the guy's taking a beating for something he didn't create. I know the feeling all 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
July 23, 2010 at 4:15 am
MegaDBA (7/22/2010)
I think what Joe points out is 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
July 22, 2010 at 12:50 pm
Things certainly got a little harsher than they should have and I guess I started it with my comment. Apologies. I meant it as a joke.
"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 22, 2010 at 12:28 pm
WayneS (7/22/2010)
Steve Jones - Editor (7/22/2010)
I do think this is a thorny issue. Would...
"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 22, 2010 at 12:22 pm
Just grouping by functional area isn't necessarilly going to help with I/O. Do you have multiple disks and multiple controllers? If not, just adding another file and filegroup isn't likely...
"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 22, 2010 at 12:19 pm
magasvs (7/22/2010)
I new I will get incorrect answer 🙂I based my answer on sys.indexes "type" column:
Type of index:
0 = Heap
1 = Clustered
2 = Nonclustered
3 = XML
4 = Spatial
I think this...
"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 22, 2010 at 11:24 am
GilaMonster (7/22/2010)
Jack Corbett (7/22/2010)
I got the answer right because of Grant's recent SQL University blog post[/url] which also lists 8 and references BOL.
I must admit, I don't agree with 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
July 22, 2010 at 11:21 am
There is no implicit conversion from DATETIME to INT. If your table has no data, drop it and recreate it. Otherwise, what you need to do is create the new...
"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 22, 2010 at 6:55 am
Ooopsie. That's what I get for using my brain instead of the Mark I Eyeball. I really need a brain upgrade. Thanks.
"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 22, 2010 at 6:06 am
I'm in agreement here. You're possibly looking at a parameter sniffing issue, where the differering parameters are getting you differing execution plans. Based on what you describe, that's pretty likely....
"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 22, 2010 at 5:48 am
Viewing 15 posts - 14,581 through 14,595 (of 22,219 total)