Read your database's transaction log and root out errors
Lumigent Technologies' Log Explorer is the first—and so far the
only—utility that reads SQL Server 7.0 transaction logs.
Microsoft has never provided a tool for reading a SQL Server
transaction log. You can use a query to display the operation
codes in the SQL Server 6.5 syslogs table, and third-party
products are available to read a SQL Server 6.x transaction log.
But because SQL Server 7.0's (and SQL Server 2000's) transaction
logs reside in their own files separate from data files, those
SQL Server releases don't have a syslogs table. As a result, SQL
Server 7.0 transaction logs have been inaccessible until the
advent of Log Explorer.  Why would you want to read a database's
transaction log? Suppose a user mistakenly deletes data. If you
know approximately when the delete occurred, you might be able
to determine which transaction log backup file or set of files
contains the operation. And if you could read that transaction
log, you could find the co