Last post Mar 24, 2016 01:41 PM by StrangerMike
Mar 23, 2016 01:39 PM|strangermike|LINK
we have no official DBA in our company. We are kind of learning as we go along.
Yesterday we started receiving an error on a database that stated the 'transaction log was full'. This database was recently setup.
I checked the recovery mode and it was set to Full, when we only needed to be set to 'Simple'. After I switched the recovery mode to Simple, we were then able to get into the application that uses the database.
I found the transaction log and it is pretty big, so I guess the act of switching recovery modes, did not truncate the transaction log file, but we are able to get into the application that uses the database now.
What should I do with the large transaction file? Can it be truncated? And how to do this?
Mar 23, 2016 02:02 PM|PatriceSc|LINK
SQL Server Management Studio allows to check the size of the log file and to shrink it if needed. More likely you'll find that most of the log file is not used any more (and won't ever) so you may want to reclaim this unused space.
Mar 23, 2016 08:58 PM|limno|LINK
You can shrink your log file to a suitable size (from SSMS ) and leave your database as SIMPLE recovery mode. No matter which mode they are in, you need to have a backup plan in place to take full bakcup regularly. It is very important.
Mar 24, 2016 01:41 PM|strangermike|LINK
thank you both
I switched the recovery mode to simple. I backed up the database and via Tasks, I ran on shrink on the log file. Everything appears to be working now.