SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Change in Recovery Model


Change in Recovery Model

Author
Message
anupamk
anupamk
SSC Veteran
SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)SSC Veteran (268 reputation)

Group: General Forum Members
Points: 268 Visits: 113
Hi,

In my Datawarehouse project(implemented 2 yrs back) we want to change the Recovery Model from Simple to Full.

What will be the impact? How the performance will be affacted. What things I need to take care of?

Thanks,
Anupam
GilaMonster
GilaMonster
SSC Guru
SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)SSC Guru (555K reputation)

Group: General Forum Members
Points: 555561 Visits: 47767
You'll need to schedule log backups. Frequency should be based on the RPO of the database mostly and on the volume of log records second.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


prettsons
prettsons
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4483 Visits: 1475
Simple recovery model allows restore database only up to the last full backup, while in full recovery model, you can get point in time recovery.

You can change recovery model from simple to full as it is desirable in any production enviornment.

however, you would have to take a full backup immediately after changing recovery model from simple to full. Also, as suggested you need to perform periodic transactiong log backup based on your workload.

SQL Database Recovery Expert :-)
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)SSC Guru (138K reputation)

Group: General Forum Members
Points: 138263 Visits: 18233
prettsons (3/26/2013)
Simple recovery model allows restore database only up to the last full backup

Up to the last differential backup actually, as long as you're taking diff backups of course ;-)

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)

Group: General Forum Members
Points: 226286 Visits: 40437
prettsons (3/26/2013)
Simple recovery model allows restore database only up to the last full backup, while in full recovery model, you can get point in time recovery.

You can change recovery model from simple to full as it is desirable in any production enviornment.

however, you would have to take a full backup immediately after changing recovery model from simple to full. Also, as suggested you need to perform periodic transactiong log backup based on your workload.


Is this really true?


You can change recovery model from simple to full as it is desirable in any production enviornment.


There may be environments where using the FULL recovery model may not be needed. I may not use it in a data warehouse environment. It would depend on the size of the data warehouse database, how often that data is loaded. I may go for a weekly full backup during a slow time for data warehouse access (perhaps on a weekend) and then run differentials after each load. Small enough database maybe a full backup after every load.

What this means is FULL recovery model may not be desirable in any production evironment. Look at your RPO and RTO requirements and your databases.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search