 |
 |
Archives of the TeradataForum
Message Posted: Thu, 01 Aug 2002 @ 19:18:36 GMT
| Subj: | | Re: Rollback on long-running update |
| |
| From: | | Anomy Anom |
<-- Anonymously Posted: Thursday, August 01, 2002 14:35 -->
| | Does any one have any experience on how to handle this? Are there any options available where one can reduce the loss of service
during a rollback? | |
| | Start dbscontrol and look at general field 10, RollbackPriority. | |
You can also use Performance Monitor to modify the account string, and therefore the priority, of the session performing the rollback.
With PSF, you can concoct even subtler potions.
| | Basically there is not a lot you can do with rollback... short of let roll baby roll... all night long...! | |
Yes, but it still may be preferable to the alternative. Recently we allowed a large update to continue rather than abort it and let it
roll back. It took six days to finish!
| |
