Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have backed up a database (full backup) and was attempting to restore as a new database (different name). However when attempting to restore it I get the following error:

The transaction log for database 'L-Test' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases.

Not really sure why that's happening. The size of the database is only 37.50MB and the logfile is set to auto grow as well.

share|improve this question
And what did you get when you looked at the log_reuse_wait_desc column in sys.databases? – Thomas Rushton Jul 2 '13 at 20:22
By "the size of the database" do you mean the size of the BAK file? – Aaron Bertrand Jul 2 '13 at 20:51
@Thomas I think this is happening as the log file is being expanded during the restore operation. So, unfortunately, there is probably not a relevant row in sys.databases. – Aaron Bertrand Jul 2 '13 at 20:56

Keep in mind that the backup does not necessarily reflect the size of the database (including the log) on disk - even if compression is not used.

You are likely trying to expand a log file that matches the size on the original database, and there is not enough space on the disk. You should check the size that the restore operation is trying to restore to looking at the size column for the files in the following query:


This may or may not match the current size of the original source database, depending on when the backup was taken and what type of operations have been performed against that database in the meantime.

If you don't have that much space to spare on the disk you're trying to restore to, you have multiple options:

  1. free space on the drive;
  2. use WITH MOVE to place the data and/or log files on a different drive with sufficient space; or,
  3. shrink the log file on the original database (this may require performing a log backup or a checkpoint to be effective, depending on recovery model) and then take a new, COPY_ONLY backup and restore that.
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.