This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Transaction Log Size

Hello Everyone,

Is there anyone realize Solarwinds and Microsoft are calculating the transaction log size different on the database ?

We are checking transaction log size with dbcc-sqlperf it's giving us a value. After that we are checking over Solarwinds but the result is not the same.

https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-sqlperf-transact-sql?view=sql-server-ver15

Both of them is trying to calculate the same thing but result is different. Is there anyone find a solution or workaround for this ?

We already talked with support and Dev team but they are saying it's correct value.

Thank you. 

Parents Reply Children
  • We are seeing on the Appinsight for SQL Application Details Page.

    Dev Team also shared the calculation of the formula.  The calculation formula is 

    TransactionLogFreeSpace * 100 / (TransactionLogSize + TransactionLogFreeSpace) AS TransactionLogFreeSpaceInPercents,

  • So what we're reporting in SAM is Transaction log free space based on the transaction log size - not the disk size.  And we're doing it on a routine basis (the last poll).

    How far off are the numbers between the two entries?  On a highly transactional database (like the SolarWindsOrion one or other OLTP databases), I can see this number varying greatly due to log write fluctuations.