Disaster recovery is deeply embedded into the design of SQL Server, and as such, it is important to carefully understand and manage your database backup policies. SQL Server databases must be backed up using the built-in BACKUP command, either natively within SQL Server or through the use of a SQL-specific, third-party tool. If no backup is done on a particular database, it is impossible to recover in case of corruption, system failure, or accidental data deletion. Regular filesystem backups are not a substitute for database backups.


Refer to the Microsoft Technet article Backup (Transact-SQL) for an overview of backup operations in SQL Server. All databases include a configured recovery model, which dictates the type of backup and restore operations that are available. In all cases, perform a full backup of any database that has never experienced a backup. In the simple recovery model, perform regular, full backups on an ongoing basis while using the full or bulk-logged recovery model. In addition, add regular log and differential backups to the full backup schedule.


Need more help? Search the Idera Customer Support Portal.

  • No labels