recovery model

Question

recovery model

sandhyarao49

SSCrazy

Points: 2215
More actions
May 26, 2008 at 9:44 am

#188166

database A is in full recovery model and the log for that database is log A.
database B is in Bulk logged recovery model and the log for that database is log B
suppose a bulk operation of 2000 record is performed on both databases A and B.
Then my doubt is both logs A and B have the same information , but point in time recovery is only possible for database A and it is not possible for database B.
Plz guide me

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 1

To the best of my knowledge, point of time recovery that includes bulk inserts, is possible only with FULL RECOVERY... and then only if you're backing up the log very frequently.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

sandhyarao49 SSCrazy Points: 2215 More actions · Answer 2

Thanks for your answer.

I want to know whether log A and log B has the same transactions or not

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 3

Maybe yes, maybe no... the Bulk Insert has to meet certain requirements to NOT be logged. Check for "Recovery Model" in Books Online for more information on the recovery models... see the following BOL url for more information on whether something get's minimally logged or not...

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/bd1dac6b-6ef8-4735-ad4e-67bb42dc4f66.htm

(Past the above into the BOL url field...)

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)