SQL Server Backup and Restore - Simple Talk

Chapter 5: Log Backups
CREATE DATABASE [ForceFailure]
ALTER DATABASE [ForceFailure] SET RECOVERY FULL WITH NO_WAIT
GO
DBCC Loginfo;
GO
Listing 5-10: Running DBCC Loginfo on the ForceFailure database.
The results are shown in Figure 5-13. The DBCC LogInfo command returns one row
per VLF and, among other things, indicates the Status of that VLF. A Status value
of 2 indicates a VLF is active and cannot be truncated; a Status value of 0 indicates
an inactive VLF.
Figure 5-13: Five VLFs for our empty ForceFailure database.
Five rows are returned, indicating five VLFs (two of which are currently active). We
are not going to delve any deeper here into the meaning of any of the other columns
returned.
Now let's insert a large number of rows (one million) into a VLFTest table, in the
ForceFailure database, using a script reproduced by kind permission of Jeff Moden
(www.sqlservercentral.com/Authors/Articles/Jeff_Moden/80567/), and then rerun
the DBCC LogInfo command, as shown in Listing 5-11.
178