Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-03-05 : 08:57:23
|
| Virginia Andersen writes "I have a Batch process where I am required to create a Pre-process backup at the begining of the Transaction (ISOLATION LEVEL SERIALIZABLE), and then do a post-process backup. I need both backups to be in the same transaction. The problem that I am having is that the second backup does not contain the changes that were created by the process within the transaction. Is there some setting I can use to get the data I want??" |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-05 : 10:37:39
|
| It's not getting the new data because that data still hasn't been committed when you run your second backup. I don't know if there is anything you can do to backup that data aside from commiting the transaction before running the second backup. Not sure if it will make a difference or not, but maybe look into nesting your transactions.Jeff BanschbachConsultant, MCDBA |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-05 : 15:10:54
|
| Also make sure that you don't have the BACKUP command within a transaction (it's not allowed, and even if it was, you DEFINITELY wouldn't want it function within a transaction that was later rolled back)Are you sure the transaction is being committed? Are you sure the second backup is successful at all? Are you doing full database backups or log backups? If they're log backups, are you doing any BULK INSERT, WRITETEXT/UPDATETEXT, or SELECT...INTO operations in the transaction? These will invalidate the transaction log, and you won't be able to do a log backup without doing a full backup first. |
|
|
|
|
|
|
Backup at the end of a Transaction (ISOLATION LEVEL SERIALIZABLE) does not get the new data