If your batch process uses transactions a rollback transaction executed on the same connection should work. If fact it if the batch process failed (and it wsa using transactions) it should have already rolled back. If not you are probably stuck restoring last nights backup and any tranaction log backups you have prior to the batch process starting. Also if it makes sense in your situation you might consider restoring the backup to a different database name and working to see what if anything is savable from your current databases and combining them. Obviously this is major surgery an wold depend on what data entry you were trying to save and if it was totally segregated from whatever the batch process munged.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.