In this article
The Model database is set up when SQL Server is installed and works as a template for new databases –settings on the Model database will be inherited by all new databases created on the system, and some settings should be configured before installing Forsta Plus in order to ensure the databases are created with the recommended options. The database properties can be adjusted in the SQL Server Enterprise Manager.
- Autogrow – should be set to allow databases to grow in size automatically when needed. If this setting is not enabled, Forsta Plus will produce errors similar to "The primary filegroup for database <db name> is full", and a larger size will have to be adjusted manually. We strongly recommend enabling the autogrow feature for both data and log files. Note: The default option is to grow the database by 1MB of the database size. This can lead to high fragmentation, so we suggest setting the initial size to 15MB, and autogrowth to 10MB. For databases that become large (10GB+), this option can be changed individually on each database to set a fixed MB size growth for each growth operation. This may prevent issues with autogrow operations timing out and causing issues on the server.
- Autoshrink – when enabled, the database system will periodically optimize database white space and shrink the file size of the database. The feature will produce quite some performance overhead, so in most cases this should be disabled, and instead periodical maintenance jobs may be scheduled to shrink databases at given times if disk space becomes an issue
- Autoclose – when enabled, the feature will automatically shut down a database when all connections to it have been closed. The setting must be disabled as it could potentially cause substantial performance overhead on the database server.
- Recovery model – Depending on the backup strategy in use, simple or full transaction logging is recommended. For full/differential database backups, simple transaction logging is sufficient, while for systems where point-in-time recovery is required, full transaction logging is required. Refer to Microsoft KB articles related to SQL recovery model for more information.
Important
Some databases (particularly [aspstate], [confirm] and [confirmlog]) can produce very large transactions logs for active systems if full transaction logging is enabled. If full transaction logging is used, setting up a maintenance plan for periodically creating checkpoints and backing up transaction logs is paramount, particularly for these two databases.