Kill without Rollback?

Question

Kill without Rollback?

John A Hamilton

Old Hand

Points: 395
More actions
January 31, 2005 at 11:30 am

#163714

I have a process a user ran against the production database that has been running for 3 days. It is an update statement run through query analyzer against the database.
Since we can continue the update from any point, is it possible to kill the process without rolling back the data?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Marvin D SSCarpal Tunnel Points: 4058 More actions · Answer 1

I have not seen any way to kill an update without a rollback sorry. Anytime you kill and update the rollback is automatically initiated. In the future you may want to break up your inserts in smaller chunks to prevent cases such as this.

Marvin Dillard
Senior Consultant
Claraview Inc

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 2

No, because then you would have inconsistend data !

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

John A Hamilton Old Hand Points: 395 More actions · Answer 3

Data consistancy isnt always bad.

The update was updateing missing data by using subqueries.

If I could have killed the process, we could pick up where it left off because it is looking for only records where the data is missing.

The user figured by starting is saturday morning it would have been done by Monday morning. Unfortunatly not.

We made a copy of the table the subqueries were running against and then deleted all the data from it. It increased speed by 6 times.

Now we need to determin if there is an issue with one of our indexes, or if the proccessing time it is related to the sheer volume of records.

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 4

- Logical dataconsistancy is a user problem.

- Physical dataconsistancy is a sqlserver problem ! This means a transaction is OK or it must be rolled back. If one cannot live with that, goback to notepad.

- If you have deleted rows, it is possible the space is still allocated to the table or file.

Filegrowth costs time ! page-allocation also but less then filegrowth !

- If you truncate a table, table-page-space is freed !