70-450 · Question #81
You are a professional level SQL Sever 2008 Database Administrator. A large financial database is hosted by the instance. The backup strategies listed below are contained by the database: - First…
The correct answer is C. You should create a database snapshot. Reasons to take database snapshots include: - Maintaining historical data for report generation. Because a database snapshot provides a static view of a database, a snapshot can extend access to data from a particular point in time. For example, you can create a database…
Question
You are a professional level SQL Sever 2008 Database Administrator. A large financial database is hosted by the instance. The backup strategies listed below are contained by the database:
- First, the performance of a full database backup is implemented once
a week.
- Secondly, the performance of a differential backup is implemented
every day.
- Thirdly, the performance of a transaction log backup is implemented
every hour. An end-of-year batch process should be implemented, and the process takes two hours to run. About five percent of data within the database will be changed by the batch process. Since you are the technical support, you are required to make sure that the batch operation can be rolled back in the shortest time, if the batch process is not approved by the Finance department. What should you do first before start the batch process?
Options
- AYou should perform a differential backup.
- BYou should create a marked transaction. And then you should perform a transaction log
- CYou should create a database snapshot.
- DYou should record the time before the batch operation. And then you should perform a
How the community answered
(15 responses)- A7% (1)
- B7% (1)
- C87% (13)
Explanation
Reasons to take database snapshots include: - Maintaining historical data for report generation. Because a database snapshot provides a static view of a database, a snapshot can extend access to data from a particular point in time. For example, you can create a database snapshot at the end of a given time period (such as a financial quarter} tor later reporting. You can then run end-of-period reports on the snapshot. If disk space permits, you can also maintain end-of-period snapshots indefinitely, allowing queries against the results from these periods; for example, to investigate organizational performance. - Using a mirror database that you are maintaining for availability purposes to offload reporting. Using database snapshots with database mirroring permits you to make the data on the mirror server accessible for reporting. Additionally, running queries on the mirror database can free up resources on the principal. For more information, see Database Mirroring and Database - Safeguarding data against administrative error. - Before doing major updates, such as a bulk update or a schema change, create a database snapshot on the database protects data. lf you make a mistake, you can use the snapshot to recover by reverting the database to the snapshot. Fleverting is potentially much faster for this purpose than restoring from a backup; however; you cannot roll forward afterward.
Topics
Community Discussion
No community discussion yet for this question.