SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 82 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

Instead, you
change just the logical device definition.
Creating a Backup Device
Create a backup device by invoking the built-in sp_adddumpdevice procedure??”for
example:
EXEC sp_adddumpdevice @devtype='disk',
@logicalname='AWBackup',
@physicalname='D:\backup\AWBackup1.bak'
EXEC sp_adddumpdevice @devtype='tape',
@logicalname='AWTapeBackup',
@physicalname='\\.\tape0'
WHY DUMP?
When developers talk about backup devices, they never use the word dump. So why are stored procedures
named sp_adddumpdevice? The answer goes back to SQL Server 6.5 and earlier, when the
concept of devices (preallocated disk space) was the norm, and the actual command to perform a
backup was DUMP DATABASE or DUMP LOG. The convention is now used for backward compatibility.
Three versions later, isn??™t it time for a more appropriate name for that stored procedure?
CHAPTER 2 n MAKING DATABASE BACKUPS 25
Dropping a Backup Device
Dropping a backup device is even simpler than creating one:
Sp_dropdevice @logicalname='AWBackup'
This command only removes the backup device definition??”it doesn??™t automatically
delete the files contained therein.


Pages:
70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94