70-450 · Question #101
You administer a SQL Server 2008 instance that hosts a large financial database. The database has the following backup strategies: - A full database backup is performed once a week. - A differential…
The correct answer is B. 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 administer a SQL Server 2008 instance that hosts a large financial database. The database has the following backup strategies:
- A full database backup is performed once a week.
- A differential backup is performed every day.
- A transaction log backup is performed every hour.
You plan to execute an end-of-year batch process that takes two hours to run. The batch process will modify about five percent of data within the database. You need to ensure that if the Finance department does not approve the batch process, the batch operation can be rolled back in minimum possible time. What should you do prior to starting the batch process?
Options
- APerform a differential backup.
- BCreate a database snapshot.
- CCreate a marked transaction. Perform a transaction log backup.
- DRecord the time before the batch operation. Perform a transaction log backup.
How the community answered
(21 responses)- A14% (3)
- B76% (16)
- C5% (1)
- D5% (1)
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} for 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 sewer 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. If 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.