What should you do to revert the CK_Catalog online database to the CK_catss_thursday snapshot?

You work as the database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. All servers on the Domain.com network run Windows Server 2003 and all clients run Windows XP Professional.
The Domain.com network contains a SQL Server 2005 database server named Certkiller -DB01. Certkiller -DB01 contains a large database named CK_Catalog which is updated every Monday and every Thursday. An online version of the CK_Catalog database is available to customers on the Domain.com e-Commerce Web site. Clive Wilson, the Webmaster of the Domain.com e-Commerce Web site is responsible for updating the online version of the CK_Catalog database. To optimize performance of the CK_Catalog online database, you create database snapshots at 5:30 PM every Monday and every Thursday. Each time you create a new snapshot, you delete the snapshot from the previous week. The two snapshots are named CK_catss_monday and CK_catss_thursday. One Tuesday morning Clive Wilson informs you that he imported the wrong data into the CK_Catalog online database. You need to revert the CK_Catalog online database to the CK_catss_thursday snapshot and allow Clive Wilson to import the correct data.
What should you do?

You work as the database administrator at Domain.com. The Domain.com network consists of a single Active Directory domain named Domain.com. All servers on the Domain.com network run Windows Server 2003 and all clients run Windows XP Professional.

The Domain.com network contains a SQL Server 2005 database server named Certkiller -DB01. Certkiller -DB01 contains a large database named CK_Catalog which is updated every Monday and every Thursday. An online version of the CK_Catalog database is available to customers on the Domain.com e-Commerce Web site. Clive Wilson, the Webmaster of the Domain.com e-Commerce Web site is responsible for updating the online version of the CK_Catalog database. To optimize performance of the CK_Catalog online database, you create database snapshots at 5:30 PM every Monday and every Thursday. Each time you create a new snapshot, you delete the snapshot from the previous week. The two snapshots are named CK_catss_monday and CK_catss_thursday. One Tuesday morning Clive Wilson informs you that he imported the wrong data into the CK_Catalog online database.

You need to revert the CK_Catalog online database to the CK_catss_thursday snapshot and allow Clive Wilson to import the correct data.
What should you do?

A.
Restore the CK_catss_thursday snapshot in Replication Monitor.

B.
Run the Transact-SQL statement: DROP DATABASE CK_catss_monday.

C.
Run the Transact-SQL statement: RESTORE DATABASE CK_Catalog FROM DATABASE_SNAPSHOT = ‘CK_catss_thursday’.

D.
Set the Restrict Access option for the online CK_Catalog database to Single.

Explanation:
When you want to revert a database back to a snapshot, you must drop any other snapshots of the database; therefore you need to drop the snapshot that you do not want to revert to.
Incorrect Answers:
A: You cannot revert a database to a snapshot in Replication Monitor. You can only revert a database to a snapshot using the RESTORE DATABASE Transact-SQL statement.
C: When you want to revert a database back to a snapshot, you must drop any other snapshots of the database; therefore you need to drop the CK_catss_monday snapshot first before you run the RESTORE DATABASE Transact-SQL statement.
D: When you run the RESTORE DATABASE
Transact-SQL statement with the FROM DATABASE_SNAPSHOT clause, SQL marks the database as ‘In restore’. When a database is marked ‘In restore’ you do not need to set the Restrict Access option to Single.
Reference:
Microsoft SQL Server 2005 Books Online (2006), Index: features [SQL Server]



Leave a Reply 0

Your email address will not be published. Required fields are marked *