You administer a Microsoft SQL Server 2012 instancethat contains a financial database hosted on a storage
area network (SAN).
The financial database has the following characteristics:
A data file of 2 terabytes is located on a dedicated LUN (drive D).
A transaction log of 10 GB is located on a dedicated LUN (drive E).
Drive D has 1 terabyte of free disk space.
Drive E has 5 GB of free disk space.
The database is continually modified by users during business hours from Monday through Friday between
09:00 hours and 17:00 hours.
Five percent of the existing data is modified each day.
The Finance department loads large CSV files into anumber of tables each business day at 11:15 hours and
15:15 hours by using the BCP or BULK INSERT commands.
Each data load adds 3 GB of data to the database.
These data load operations must occur in the minimum amount of time.
A full database backup is performed every Sunday at10:00 hours.
Backup operations will be performed every two hours(11:00, 13:00, 15:00, and 17:00) during business hours.
You need to ensure that the minimum amount of data is lost.
Which recovery model should the database use?
A.
FULL
B.
DBO_ONLY
C.
CONTINUE_AFTER_ERROR
D.
CHECKSUM
E.
NO_CHECKSUM
F.
SIMPLE
G.
Transaction log
H.
SKIP
I.
RESTART
J.
COPY_ONLY
K.
NORECOVERY
L.
BULK_LOGGED
M.
Differential
N.
STANDBY
Explanation:
I’d still prefer bulk logged
Reference: http://msdn.microsoft.com/en-us/library/ms189275.aspx
what is the correct answer ? BULK_LOGGED ??
L
Full should be used. It is the only recovery model that supports Point-in-time recovery. Thus satisfying minimum amount if data lost.
Bulk logged satisfy the requirements: minimun amount of data lost is guaranteed by differential and/or tlog backup.
Point-in-time recovery is related to the need of restoring data oldest than the newest available.
I’d rather say its FULL, cause the only measurement is the “loss of data”. If you dont want to loose any date you need to able to recover to a point of time. Cause there could be a data loss a couple of minutes after a differential backup. In this case you could loose less data if you have a point-in-time recovery, which is only supported by Full Backup:
https://msdn.microsoft.com/en-us/library/ms189275.aspx
FULL
The correct answer is Bulk-Logged due to the constraint in the question as follows: These data load operations must occur in the minimum amount of time.
Therefore, the best choice is Bulk-Logged