Viewing 15 posts - 13,591 through 13,605 (of 22,219 total)
pdanes2 (1/14/2011)
"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
January 17, 2011 at 6:13 am
To see if a resource is locked, you do have to query the server. To see if a lock is blocking another user, again, you have to query the server....
"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
January 14, 2011 at 12:46 pm
homebrew01 (1/14/2011)
"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
January 14, 2011 at 12:38 pm
pdanes2 (1/14/2011)
Grant Fritchey (1/14/2011)
I would be very, very, very careful about using NOLOCK. It seems like it solves problems, but it can introduce bad data.
Hmm, yes, I see what you...
"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
January 14, 2011 at 10:58 am
zerolan22 (1/14/2011)
I used the 2 bigints as a combined, primary clusered index with no performance improvements, rather the opposite, it was even slower on
inserts....
"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
January 14, 2011 at 10:30 am
I haven't looked at the exec plan, but first off, get a clustered index on the table. Absolutely. Figure out what the right place to put it would be 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
January 14, 2011 at 9:30 am
I would be very, very, very careful about using NOLOCK. It seems like it solves problems, but it can introduce bad data. By that I mean, repeated rows, missed rows,...
"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
January 14, 2011 at 9:24 am
Yep, I've done it. It can work great. It requires a lot of discipline, but you can do it. I've written a couple[/url] of articles[/url] on it (although they're 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
January 14, 2011 at 7:58 am
It sounds like it could be contention, probably blocking, from uncommitted transactions. While you're in that stuck position, run this little query:
SELECT der.blocking_session_id,
...
"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
January 14, 2011 at 7:49 am
Gotta be a difference in the stats. Should be evident by having different execution plans.
"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
January 14, 2011 at 7:44 am
1) Nope, the locks are usually held for the duration of the transaction in case of rollback. If you've got a cursor in a trigger (oy), then the transaction is...
"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
January 14, 2011 at 7:38 am
I would take a look at your execution plans from the merge statement. Something is causing this to slow down. You're working in a very small database, so you shouldn't...
"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
January 14, 2011 at 7:35 am
Nope. Not with the log in simple recovery. Now, if the log were in full recovery you could either backup the log & retrieve it from there, or use one...
"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
January 14, 2011 at 7:29 am
Just so you know, deleting data from a SQL Server database doesn't reduce the file allocations for that database.
"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
January 14, 2011 at 7:26 am
CirquedeSQLeil (1/13/2011)
Grant Fritchey (1/13/2011)
My personal preference for this, Red Gate's SQL Prompt Pro. Fantastic tool. Does a heck of a lot more than just format the code too.
Same recommendation I...
"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
January 13, 2011 at 11:54 am
Viewing 15 posts - 13,591 through 13,605 (of 22,219 total)