Transaction Log File (*.ldf for a HEAT or ConfigDB database) is growing rapidly -- How to manage?

Version 1

    Details

    Transaction Log File (*.ldf for a HEAT or ConfigDB database) is growing rapidly -- Why? What are the contents?  How do we manage them?


    Resolution

     

    Transaction log files are purely a product of SQL itself, and are not maintained by ITSM or HEAT. They are simply indicative of a large number of transactions. This may be produced for any number of normal reasons, including (but not limited to):

    • Large number of records (Incident, Service Request, Task) handled routinely
    • Heavy amount of automation (Business Rules, complex or numerous workflows)
    • Frequent or heavy amounts of integration (Inventory management, etc)

     Further information can be found at:
     
     
    And further information on shrinking it:
     

    If after review by your DBA, there are specific concerns about certain transactions, certain table sizes or contents, or other log files specific to HEAT, please contact Support via the normal channels, with specific details.