You administer a Microsoft SQL Server 2012 instance that 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 a number 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 at 10: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:
http://msdn.microsoft.com/en-us/library/ms189275.aspx
.. answer lacking up to now !
0
0
Correct answer is L
0
1
Why not A?
Yes, question says “These data load operations must occur in the minimum amount of time”, so BULK_LOGGED makes sense, but the final question is “You need to ensure that the minimum amount of data is lost”. With BULK_LOGGED you lose bulk operations in the backups performed every 2 hours, with FULL not, it’s correct?
https://technet.microsoft.com/en-us/library/ms190692%28v=sql.105%29.aspx
0
0
Stupid Question science Full and Bulk and Copy_Only
All of them are right
0
0
Man, I see you writing “science” instead of “since”, its annoying
0
0
yeah, I have seen that in many replies too 🙂
BTW, Mohamed, Copy_Only is not a recovery model, it’s a type of backup.
0
0
I would go with FULL. It is the only model that allows Point In Time recovery.
0
0
Yes you are right the full backup will be the best solution science we need minimum data loss
0
1
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/73c2e9d7-2e9d-4c81-921d-eed5d669613a/test-question
0
0
Yet another tricky question… Full is indeed the only option with point in time recovery, allowing minimal data loss, but I would still answer BULK_LOGGED, because with FULL you can’t meet the “data load operations must occur in the minimum amount of time” requirement and, more importantly, the 10GB transaction log would certainly not be big enough.
0
0
This question is about Recovery Model, not Backup type. If they don’t want loose data the Recovery Model must be FULL. It’s my opinion.
0
0
Man, I see you writing “loose” instead of “lose”, its… interesting.
0
0
The finance department loads large CSV files (that’s a bulk operation) hence the recovery model should be Bulk_Logged
0
0
A. Full
0
0
I agree A. Full Recovery Model
0
0
COULD WE GO HOME NOW CRIS?
0
0
A very good reason to have FULL Recovery model…
Scenario 1: “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”
Switch to BULK Recovery model to perform the data load & revert back (to FULL), to minimize data loss:
Scenario 2: “The Finance department loads large CSV files into a number of tables each business day at 11:15 hours and 15:15 hours by using the BCP or BULK INSERT commands.”
0
0
Answer is A. Full Recovery Model.
Bulk Logged Recovery model is not recommended in day-to-day operations.
Best solutions for this situation is to switch the recovery model from Full to Bulk Logged from 11:15 to 15:00 hours daily.
To minimize data loss, Full Recovery model is better option.
https://msdn.microsoft.com/en-us/library/ms190217.aspx
0
0
I would say BULK_LOGGED
because the say it must occur in the minimum
These data load operations MUST occur in the minimum amount of time
while FULL recovery gives you point in time recovery, still BULK_LOGGED gives you a full restore option when the DB fails.
and point in time recovery is not a requirement.
0
0
answer is F: continue afte eror
0
1