Using dump and load transaction When Shrinking Log Space

The size of a log might change during a dump sequence in which the database is first dumped, and then transaction log dumps are performed periodically.

This is particularly true, for example, if the log segment is increased to accommodate the increased volume of logging that is done by a fully logged select into, and then the log is shrunk after completion of the command to return the log to its former size. Use these guidelines to load such a dump sequence:

Create the database that is being loaded from the dumps with the largest size during the dump sequence. Determine this by executing dump tran with headeronly on the last transaction dump to be loaded.
Shrink the log to the size needed only after the transaction log sequence has completed and you have brought the database online.

This example follows the numbered steps described in Example Using dump and load transaction.