when we started using the ARM, I logged everything without limit for testing, which made the database file very large.
The database file is now about 80GB, but 40GB of this is whitespace.
Is there a best practice to shrink the SQL file again?
I know that it is generally not recommended to shrink SQL files because it can worsen the performance, but the database will never grow back to 80GB, so I really want to get the whitespace back!
The log file "ARM_log.ldf" is now 12GB in size and gets bigger in irregular intervals.
Sometimes it does not grow for days. But from yesterday to today it grew again almost 2GB, although we didn't make any big changes in the ARM.
I am of course aware that the size of the log file depends on the settings of the ARM and also on what is being logged, but is it normal that the log sometimes doesn't grow at all and then suddenly so much?
Is 12GB too big for a log file?
there is no problem with shrinking the database file(s). Just use the SQL Server tools to do so.
Concerning your transaction log file perform transaction log backups and your problem's solved.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.