Viewing 15 posts - 19,096 through 19,110 (of 22,226 total)
Don't use transactions on the read statement. There's no need for them anyway.
"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
December 12, 2008 at 4:28 am
The statement you have there is an extended property. It doesn't create functions. Instead it is used to document and describe objects already created within the database. You can lookup...
"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
December 12, 2008 at 4:27 am
You can check the @@rowcount to verify how many, if any, records were deleted. Or you can use the OUTPUT clause to capture specifically which records were deleted.
"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
December 12, 2008 at 4:22 am
As Jack explained to you, without some specifics, there's almost no way to address your issue.
Speaking in general terms, using a cursor to select records is almost always a mistake....
"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
December 12, 2008 at 4:19 am
I'm actually not entirely sure what you're asking. Do you mean something like: Always join on the key, the whole key. Or are you looking for tricks with XML execution...
"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
December 12, 2008 at 4:02 am
jeffrey_bryant (12/11/2008)
Unfortunately the Dev...
"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
December 11, 2008 at 1:38 pm
Got me beat. I've only been driving for 31 years. I've got the scars from the one major accident on the bike.
"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
December 11, 2008 at 1:00 pm
And even as you hit the limitations on a single table inside a single database on a single server, you can start to look at partitioning and parallel processing using...
"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
December 11, 2008 at 12:52 pm
It depends.
Is there going to be a lookup value:
08 A
As well as the value:
07 A
If so, then the year should probably be part of the PK of the lookup table...
"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
December 11, 2008 at 11:59 am
Yeah, maybe that's what I read too. I know I saw that it's going to more and more standard, if not required. So I'm working it into my code now....
"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
December 11, 2008 at 10:26 am
I'd say it's a good habit to get into. If you use CTE's you must use a semi-colon terminator on the statement preceding the CTE. Microsoft has said they're going...
"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
December 11, 2008 at 9:30 am
Roy Ernest (12/11/2008)
Kishore.P (12/10/2008)
Gauthama Kolivad (12/10/2008)
As Gail Shaw mentioned if...
"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
December 11, 2008 at 9:17 am
Lynn Pettis (12/11/2008)
"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
December 11, 2008 at 9:11 am
You might want to try using TOP(1) with an ORDER BY. If you're referencing an index, the TOP (1) is pretty consistently faster than the MAX.
"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
December 11, 2008 at 8:17 am
If it makes you feel better I've been hit, while stopped, not stopping, I've been sitting still, waiting, four times over the last 10 years. You're not alone.
Luckily, I drive...
"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
December 11, 2008 at 7:13 am
Viewing 15 posts - 19,096 through 19,110 (of 22,226 total)