Learn how and when to adjust database generation numbers after reloading dumps.
When you reload a database dump, the database generation number is included in the restored database. Since the database generation number is also stored in the RSSD of the Replication Server that manages the database, you may need to update that number so that it matches the one in the restored database.
However, when you reload a transaction log, the database generation number is not included in the restored log. For example, assume the following operations have occurred in a database:
Operation |
Database generation number |
|---|---|
database dump D1 |
100 |
transaction dump T1 |
100 |
dbcc settrunc('ltm', 'gen_id', 101) |
101 |
transaction dump T2 |
101 |
database dump D2 |
101 |
If you reload database dump D1, database generation number 100 is restored with it. If you reload transaction dump T1, the generation number remains at 100. After transaction dump T2, the generation number remains at 100, because reloading transaction dumps does not alter the database generation number. In this case, you need to change the database generation number to 101 using the dbcc settrunc command before having RepAgent scan transaction dump T2.
However, if you load database dump D2 before resuming replication, you do not have to alter the database generation number, since the number 101 is restored.