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 416 | Next

James Luetkehoelter

"Pro SQL Server Disaster Recovery"

It??™s extremely fast, although any data inserted, updated, or deleted since the
snapshot was created will be immediately lost.
Creating Database Snapshots
Since they behave as read-only databases, it??™s no surprise that you create snapshots using
the CREATE DATABASE command:
CHAPTER 9 n DATABASE SNAPSHOTS 231
CREATE DATABASE AdventureWorks_SS ON
(NAME=AdventureWorks, FILENAME='D:\data\AW.ss')
AS SNAPSHOT OF AdventureWorks
As opposed to a normal CREATE DATABASE statement, the NAME option here refers to the
logical name of the source file, not the logical name to be assigned to the snapshot. Note
that I??™m already using a naming convention of DBName_SS for the snapshot.
You must create a snapshot file for each file in the database. So if you have three files
in the AdventureWorks database, the command would look like this:
CREATE DATABASE AdventureWorks_SS ON
(Name=AdventureWorks_Data1, Filename='D:\data\AW1.ss'),
(Name=AdventureWorks_Data2, Filename='D:\data\AW2.ss'),
(Name=AdventureWorks_Data3, Filename='D:\data\AW3.ss')
AS SNAPSHOT OF AdventureWorks
Essentially, the database snapshot needs to look physically like its source database
(with the exception of the transaction log).


Pages:
404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428
hotel jelenia góra Russian bride Free English grammar and study guid powiekszenia wielkoformatowe counter strike 1.6