But you cannot use SQL Server restore on the backups. Note: You can perform a file-based or a disk-based backup on the mssqlsystemresource.mdf file by treating the file as if it were a binary (.exe) file, instead of a database file. Therefore, SQL Server cannot back up the Resource database. The Resource database resides in the mssqlsystemresource.mdf file, which contains only code. msdb also contains history tables such as the backup and restore history tables.Ī read-only database that contains copies of all system objects that ship with SQL Server The database used by SQL Server Agent for scheduling alerts and jobs, and for recording operators. Because model is small and rarely changes, backing up the log is unnecessary. The template for all databases that are created on the instance of SQL Server.īack up model only when necessary for your business needs for example, immediately after customizing its database options.īest practice: We recommend that you create only full database backups of model, as required. We recommend a regular backup schedule, which you can supplement with an additional backup after a substantial update.

The database that records all of the system level information for a SQL Server system.īack up master as often as necessary to protect the data sufficiently for your business needs. The following table summarizes all of the system databases. Backups of these system databases let you restore and recover the SQL Server system in the event of system failure, such as the loss of a hard disk. If any database uses replication on the server instance, there is a distribution system database that you must also back up. The system databases that you must always back up include msdb, master, and model. Several of the system databases must be backed up after every significant update. SQL Server maintains a set of system-level databases, s ystem databases, which are essential for the operation of a server instance.

Backup master database