Search
  • Repost - originally posted 29-05-2012
    • Aug 13, 2017
    • 1 min read

Model database recovery setting


We see a lot of databases in full recovery that don't need to be. Why? Because the default for the model database (used as the template for creating databases) is full recovery model. This can cause issues with very large transaction log files when the transaction log never gets backed up. To avoid this you can change the model databases' recovery model to simple. Any databases created after this change will then be created in simple recovery model. You would have to change any databases created before this to simple recovery model as well (as long as they need to be in simple recovery).


5 views0 comments

Recent Posts

See All

Standardise database sizes and automation

The default setting for the initial sizing of data and log files (and their autogrowth) is not adequate. I like to make sure that we set standard sizes for our data and log files - plus standard sizes

Migrating SSIS packages to AWS

We are currently migrating a large amount of SSIS packages (SQL Server 2008R2) to SQL Server 2016 at AWS. It has been a learning exercise to get these packages running. What we have learnt (so far) is

Autoclose and autoshrink - set them to off

By running a simple check of your database settings (use helpdb or query sys.databases) you may find databases that are set to autoclose and/or autoshrink. If so, you should change these settings as p