Hi,
we are running a mssql server 2005.
The past couple of days we have luckily noticed the logfile for one of our main databases has grown out of proportion (About 4GB a day).
My gut tells me there is something wrong with the way our new backup solution is set up, but when I went through the logs and setup with them, we could not find a single error or problem.
We managed to free some space on the server by removing a lot of old gunk, but are still stuck in a situation where the log is growing out of hand.
My question is therefore, what do I do?
FYI. I tried doing a t-log backup of one of our smaller databases, and the possible size to shrink it went from 1% to 99% after that. Can it be as simple as to setup T-log backup separately (Thereby getting the truncating) and running a shrink command locally in the server management?