SEI SQL Server Best Practice

Does anyone know the best practice for SEI such as maintenance plans? Our SQL server database transaction log file it is huge. 487321216 KB. I also noticed that the initial database file for the log is 475900 MB. That answers why the file size will reset to a large amount. Does it has to be set to this?

  • 0

    Hello,

    I think generally out of the box the initial size is 256 for the SEI_log files, but max size is pictured below and auto growth is enabled. I suggest setting it back to a smaller size of 256 and keep an eye on the logs moving forward.

  • 0

    You need to make sure you are scheduling regular transaction log backups that will allow you to manage the size of your log files. 

  • 0

    The SEI database does not contain transactional data, this hosts the Central Point - i.e. SEI users, reports, process design. I would set this to Simple recovery rather than Full and schedule a backup of say weekly or daily if you are doing a lot of amendments to SEI. I would then shrink the logfile to a much smaller size say 10% of the database - 70Mb with 25Mb growth. I would also increase the database growth from 1Mb to 50Mb