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


Changing recovery model


Changing recovery model

Author
Message
Anbarasan.Thangaraju
Anbarasan.Thangaraju
SSC Rookie
SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)

Group: General Forum Members
Points: 49 Visits: 21
Hi,

Do I have any impact on changing recovery model in SQL Server 2005 when the database is online? More over is there any impact in changing the Initial size of the log files (Currently the Recovery model is FULL).

Thank You
Chandra Sekhara Vyas Dhara
Chandra Sekhara Vyas Dhara
SSCertifiable
SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)

Group: General Forum Members
Points: 5077 Visits: 1149
If you switch from the full recovery model to the simple recovery model you break the backup log chain. Therefore, strongly recommend that you back up the log immediately before switching, which allows you to recover the database up to that point. After switching, you need to take periodic data backups to protect your data and to truncate the inactive portion of the transaction log.

You can increase the size of log file



Anbarasan.Thangaraju
Anbarasan.Thangaraju
SSC Rookie
SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)SSC Rookie (49 reputation)

Group: General Forum Members
Points: 49 Visits: 21
Hi,

Thanks for the reply, do I have any impact on changing the database recovery model while the database is in live. And more over I have the Initial size of log files is 50 GB I need to reduce it to 50 MB is that will create any problems.

Thank You
GilaMonster
GilaMonster
SSC Guru
SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)

Group: General Forum Members
Points: 222499 Visits: 46291
No impact other than that you will no longer be able to take log backup and hence will not be able to restore to a point-in-time after switching to simple. Also if you are running database mirroring you will not be able to switch from full recovery

You can shrink the log to 50MB, but if the DB is active there's every chance it will grow again. 50MB is very small for a transaction log for an active database.

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


DB Diva
DB Diva
Valued Member
Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)Valued Member (70 reputation)

Group: General Forum Members
Points: 70 Visits: 22
What would happen if I switched from Full to Simple to Full in a stored procedure?
When I back up the transaction log after I set it back to Full, would it be able to know that there was a full database backup (.bak)? I am running SQL Server 2008.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)

Group: General Forum Members
Points: 222499 Visits: 46291
Please post new questions in a new thread. Thank you.

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


Sean Perkins
Sean Perkins
SSC Veteran
SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)SSC Veteran (290 reputation)

Group: General Forum Members
Points: 290 Visits: 201
GilaMonster (9/17/2008)
No impact other than that you will no longer be able to take log backup and hence will not be able to restore to a point-in-time after switching to simple. Also if you are running database mirroring you will not be able to switch from full recovery

You can shrink the log to 50MB, but if the DB is active there's every chance it will grow again. 50MB is very small for a transaction log for an active database.


How much of a performance hit (a little, moderate, A LOT, don't do it, etc.) is there from shrinking the log file? The reason I ask is I'm faced with a situation where a production database has a much larger log file than is necessary. The database in question is a production database and it is pretty much used 24/7, so I'm attempting to find out if it is 'okay' or feasible to perform the action of shrinking a 100 GB .ldf during production hours.

The following was suggested to me in order to fix the matter:

1. Backup the TLOG
2. Change DB from Full to Simple
3. Change the initial size of the TLOG to something much smaller
4. Perform the log shrink
5. Change from Simple to Full
6. Perform full backup of DB to start log chain

Is this proper? If not, what would your process be to fix this matter?


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One of the greatest tragedies in life is to lose your own sense of self and accept the version of you that is expected by everyone else.

GilaMonster
GilaMonster
SSC Guru
SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)

Group: General Forum Members
Points: 222499 Visits: 46291
GilaMonster (4/11/2011)
Please post new questions in a new thread. Thank you.


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


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