Viewing 15 posts - 20,101 through 20,115 (of 22,219 total)
Shiraz (6/23/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
June 23, 2008 at 7:10 am
I get into work at 7AM. That gives me a good hour and a half before other people start coming in. It's the only way I know to get 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
June 23, 2008 at 6:23 am
Table variables have locks on them 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
June 20, 2008 at 7:41 am
You can... But it could lead to problems. You just have to use a table hint to control the locking mechanism.
UPDATE dbo.Mytable
WITH (ROWLOCK)
SET MyCol= 'SomeValue'
...
Be VERY careful doing stuff like...
"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
June 20, 2008 at 6:59 am
FYI, this is a repost of another discussion going through the same perambulations over here.
http://www.sqlservercentral.com/Forums/Topic520048-338-1.aspx
"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
June 20, 2008 at 6:27 am
Do you have to have a title? Grand-High-Worshipful-Poobah-and-Support?
Seriously it sounds like you're the "IT Guy." I did that for a time. I wrote WordPerfect macros, designed databases, ran networks, punched...
"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
June 20, 2008 at 6:23 am
It's just a straight-forward cost/benefit analysis along with risk and mitigation. Do you need the new functionality or is it nice to have? You need it. How big is 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
June 20, 2008 at 6:19 am
Locking is determined by the query engine. It always goes with a least cost lock. From the sounds of things, you don't have too much data in the table so...
"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
June 20, 2008 at 6:09 am
Everyone has covered it so well up to this point, especially Phil Factor's bit. The one technical thing I would add is that a new DBA must learn the logical...
"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
June 20, 2008 at 5:58 am
From the BOL:
KEY = Lock within an index that protects a range of keys in serializable transactions.
You're locking a range when what you really want is to lock a row.
"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
June 20, 2008 at 5:43 am
Even though GSquared eliminated the cursor, there are still other optimizations pointed out by others that can be done to the proc.
"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
June 20, 2008 at 5:31 am
You're using the parameter twice, once to set & once to search. It can't be done like that. You have to refer to the column twice, but if you have...
"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
June 20, 2008 at 5:28 am
anjan.ashok (6/19/2008)
CREATE PROCEDURE sp_replace_value (
@strcvalue varchar(100),
@strdesc nvarchar(100)
)
as
update testtbl set value=@strconfigvalue,desc=@strconfigdesc where value=@strconfigvalue
here assume we have...
"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
June 19, 2008 at 1:09 pm
You should be able to take the same structures that I supplied and modify it for a different column and/or data type. It all works the same way.
UPDATE table
SET col1...
"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
June 19, 2008 at 11:51 am
This was a cross-post. Answers there too:
http://www.sqlservercentral.com/Forums/Topic520048-338-1.aspx
Please don't cross-post.
"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
June 19, 2008 at 11:38 am
Viewing 15 posts - 20,101 through 20,115 (of 22,219 total)