August 12, 2004 at 10:51 am
I have a very long running transaction (> 19 hours) that I want to kill. Does anyone know a way of preventing SQL from rolling a transaction back?
August 13, 2004 at 9:50 am
There are ways, but there is NO WAY of doing this while still ensuring transactional consistency of your data file(s). I would contact Microsoft PSS before attempting this.
Corie Curcillo
MCT, MCDBA, MCSD
August 13, 2004 at 10:00 am
We just let the transaction roll back.
Out of interest, what are the ways you mention?
August 13, 2004 at 10:32 am
Without sounding cliché, PLEASE DON’T TRY THIS AT HOME!
You could, but I wouldn’t recommend, stopping the MSSQLService, making a copy of your data file(s) only, and re-attaching only the data file(s) as a new database. If done through EM, I believe that it offers to create a new TransLog for you, warning that “Trans Consistency may be lost”, which is true.
The database may come back as being in suspect mode. There are plenty of articles on re-attaching a “suspect” database. For example:
http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20726411.html
Again, this is suggested only as a last resort, and I would encourage anyone to contact PSS before proceeding w/ any of these courses of action.
Corie Curcillo
MCT, MCDBA, MCSD
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply