Inventory Pro offers a view of transaction history plus usage & inventory numbers.
The transaction log is an integral part of every SQL Server database. It contains log records produced during the logging process in a SQL Server database. The transaction log is the most important component of a SQL Server database when it comes to the disaster recovery – however, it must be uncorrupted. After each database modification – transaction occurrence, a log record is written to the transaction log. All the changes are written sequentially
The transaction log stores every transaction made to a SQL Server database, except some which are minimally logged like BULK IMPORT or SELECT INTO. Internally it is split into the smaller parts called Virtual Log Files (VLFs). When one VLF becomes full logging continue to write into the next available in the transaction log. The transaction log file can be represented as a circular file. When the logging reaches the end of the file it starts again from the beginning, but only if all the requirements have been met and the inactive parts have been truncated. The truncation process is necessary to mark all inactive parts so they can be used again and overwritten
You can view the statistics of the transaction log backup job in the History view or in the Home view in Veeam Backup & Replication. In the statistics window, you can examine the overall statistics for the transaction log backup job, as well as view per-VM information. The Statistics Log (Statlog) report creates statistical transaction logs that contain history transactions from which specific patron and title information is removed WorkFlows reports are used to manage and review transaction logs, and as well as to extract statistical data.