• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 199
  • Last Modified:

simple backup not available in management studio

I have a database that is scheduled to backup once/day.  I would like to reduce the log file size. I tried doing transaction log backups but the trn file created was 37GB. I tried to change the scheduled backup to be a simple recovery model but Management Studio/Maintenance plan/backup only allows me to select Full, Differential or Transactional. We don't need hourly transaction backups on this problem database. A daily backup will suffice. Our most important database is larger and has hourly transaction backups. Here is a comparison of this problem database with our bigger production database.
Problem db file sizes               Production database file sizes
ldf  37                                         1
mdf  4                                         5
bak  3                                         5 (including trn files)    
There aren't a huge number of transactions going on in the problem database.
How can I schedule a simple backup in Management Studio?
  • 2
1 Solution
Hi dwiseman3,
>>>I tried to change the scheduled backup to be a simple recovery model but Management Studio/Maintenance plan/backup only allows me to select Full, Differential or Transactional <<<
It sounds as though you want to change the recovery model of your database as well as your backup method.  If you right click the database select "properties" and the select "options" you can see the recovery model  drop down list.  changing this to simple will mean that your log file autotruncates, this would mean you can no longer do transaction log backups and should help to maintain your log file size (depending on your application)
Once this is done you would need to change your backup maintenance plan to a full backup once per day - you can deselect transaction and differential options if you don't need them.
Do make sure you understand the consequences of changing these option before you proceed and make sure you have a good (tested) backup.  That said everything is pretty risk free if you know what you are doing
dwiseman3Author Commented:
I see what you're saying. Will changing the recovery model 'midstream' do any damage?
Nope, that will be fine - essentially all you are losing by moving to a simple recovery model is the facility to recover data to the second which you said is not important.  The database will carry on working as normal.  Assuming the application uses small transactions then you could also look at shrinking the log file to a smaller size to better conserve disk space, the snippet below will do this (it is best to do this straight after the log has been truncated), the code below is straight out of SQL BOL (books on-line).
You want to size the database files so they grow as little as possible, this will minimise file fragmentation on the disk - unless you know the growth rates already it easiest to note this over time.

USE yourDatabase;
-- Truncate the log by changing the database recovery model to SIMPLE.
-- Shrink the truncated log file to 1GB.
DBCC SHRINKFILE (yourDatabase_Log, 1024);

Open in new window

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now