Contact Us

Few days ago I have been asked for help in process of installation a SCOM. Admins wasn’t been able to install some parts of this system because installation wizards reports some unexpected errors.

When I arrived to the SQL instance I found something interesting which ensured me that we should talk more about purpose of model database.

Please remember model is a template on which all newly created databases are made. User databases inherit properties of the model (for example recovery model), file size and file growth settings and also all objects created in the model (tables, functions, schemas, stored procedures, etc…).

Only if you explicitly specified settings in process of database creation will overwrite model default settings. So keep in mind if you left model database for example with full recovery model, every newly created database will require backup of transaction logs on regular basis.

Misunderstandings the concept of model db like this could lead (in case of recovery model=FULL) to unexpected growth of transaction log.

In my case I have got an instance with model db filled with user data (780MB in tables). It means every newly created database will have a copy of those data by default. Because model is a template database you know Smile. So when the wizard tried to create database for SCOM sized to 500MB it will always fail because minimum size of new database must be greater or equal than model database.

So remember this concept and protect you and your SQL server from those issues in the future.

More tips and tricks

SMT 1.2 version is out
by Michal Tinthofer on 09/02/2021

Releasing SMT 1.2 to you right now! Check the details.

Read more
Turning Hours into Minutes: How We Solved a SQL Server Indexing Nightmare
by Michal Kovaľ on 16/04/2026

In the world of database administration, index maintenance is a necessary evil. Done right, it keeps your queries snappy; done wrong, it becomes a resource-hungry monster that eats your maintenance window alive.

Read more
Issues with Service Pack Install
by Michal Tinthofer on 13/04/2012

Recently I had some issues with SQL server 2008 R2 service pack 1 installation. From first perspective it looks like an issue with corrupted installation package, but true issue was somewhere else. It was a windows installer.

Read more