Viewing 15 posts - 13,606 through 13,620 (of 22,224 total)
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
Sure, you can use a TOP 1 with an ORDER BY. Something like this:
SELECT y.whatever
FROM MyTable
WHERE ID = (select top(1) ID
from mytable
order by mydate desc) as y
--or in a join...
"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:51 am
It basically means that the statement in question is moving lots of data, either in (writes) or out (reads) of the server. What you do about it really depends on...
"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 10:31 am
TheSQLGuru (1/13/2011)
Not true Grant!! I can ALWAYS make time for...
"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 10:26 am
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.
"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 7:54 am
It just has to be a series of TSQL statements. I'd just suggest wrapping it in a transaction so that you know the data was moved successfully prior to deleting...
"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 7:50 am
Just curious, have you tried using the Import Data Wizard? I'm not sure it will meet your needs or not, but you can frequently get a lot more error information...
"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 7:47 am
I agree. It sounds like you're in a situation where replication would work better.
As far as Red Gate's SQL Backup goes, yes, you can restore objects and rows if 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
January 13, 2011 at 7:36 am
SQLkiwi (1/13/2011)
Grant Fritchey (1/13/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 13, 2011 at 7:18 am
Koen (da-zero) (1/13/2011)
Grant Fritchey (1/13/2011)
Koen (da-zero) (1/12/2011)
TheSQLGuru (1/12/2011)
I am curious what you mean by "advisor" here. Hopefully you do NOT mean Database Tuning Advisor!! Avoid that like 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
January 13, 2011 at 6:16 am
Koen (da-zero) (1/12/2011)
TheSQLGuru (1/12/2011)
farax_x (1/12/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 13, 2011 at 6:00 am
Viewing 15 posts - 13,606 through 13,620 (of 22,224 total)