In fact, a copy only backup uses the BACKUP command just like a DUMP backup does, but appends the COPY_ONLY argument.Ĭopy only backups were first introduced in SQL Server 2005, and serve as a mechanism for creating a one-off backup that does not interfere with the normal backup sequence (from a transaction log file processing standpoint). There are also a variety of management and monitoring capabilities that are supported by the command.Ĭopy backups, which are sometimes referred to as copy only backups, are a variation on dump backups. An administrator can use these commands to perform full, incremental, or differential backups. Whether an administrator uses the DUMP command or the BACKUP command, dump backups are very flexible. SQL Server databases and log files can be backed up by using the BACKUP DATABASE and BACKUP LOG commands respectively. The BACKUP command has largely replaced the DUMP command. Similarly, transaction logs could be backed up by using the DUMP TRANSACTION command. An administrator could back up a database by using the DUMP DATABASE command. Originally, the Dump statement provided a way for administrators to backup SQL Server databases and transaction logs.
As a tool, Dump refers to a command that is supported natively by Microsoft SQL Server.Īlthough the Dump command still exists in SQL Server today, it is actually a legacy tool that exists solely for backward compatibility purposes. As a technique, dump refers to dumping SQL Server data to backup. Two of the more common techniques for example, are copy and dump.ĭump can be thought of as either a tool or a technique.
In addition to there being a diverse collection of tools available for SQL Server backups, there are a variety of backup techniques that can be applied. As is the case for other database platforms, there are a wide variety of tools and techniques available for protecting SQL Server, ranging from native built-in tools to third party commercial backup applications. Organizations that use Microsoft SQL Server sometimes struggle with how best to protect their SQL databases against accidental data loss. Last week I wrote about how easy it is to protect a SQL environment with Cohesity.