|
|
|
|
When should I backup the master database? Back
If information in master has been changed , you should backup the master database .
If master is not backed up after it changes, any changes since the last backup are lost.
if the backup is restored. For example, if a user database is created after master is backed up, tables and data added to the database, and then master is restored because of a hard disk failure, the user database will not be known to SQL Server because there are no entries in the restored master database for this new user database.
The types of operations that cause master to be updated, and that require a backup to take place include:
Creating or deleting a user database.
If a user database grows automatically, by virtue of the autogrow feature, to accommodate new data, this does not affect master. Adding and deleting files and filegroups does not affect master.
Adding logins or other login security-related operations.
Database security operations, such as adding a user to a database, do not affect master.
Changing any server-wide or database configuration options.
Creating or removing backup devices.
Using SQL Server Enterprise Manager to perform any of these operations.
Configuring the server for distributed queries and remote procedure calls, such as adding linked servers, or remote logins.
|
|
|
Home