Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Changing recovery model Expand / Collapse
Author
Message
Posted Tuesday, September 16, 2008 11:55 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 27, 2009 2:47 AM
Points: 17, 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
Post #570750
Posted Wednesday, September 17, 2008 12:32 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 8:09 AM
Points: 3,792, Visits: 1,083
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



Post #570761
Posted Wednesday, September 17, 2008 12:36 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, April 27, 2009 2:47 AM
Points: 17, 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

Post #570764
Posted Wednesday, September 17, 2008 12:57 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:31 AM
Points: 40,177, Visits: 36,578
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 2008, MVP
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

Post #570774
Posted Monday, April 11, 2011 9:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 26, 2012 11:51 AM
Points: 8, 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.
Post #1091552
Posted Monday, April 11, 2011 9:59 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:31 AM
Points: 40,177, Visits: 36,578
Please post new questions in a new thread. Thank you.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1091558
Posted Wednesday, September 10, 2014 1:35 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:24 AM
Points: 11, Visits: 75
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?
Post #1612371
Posted Wednesday, September 10, 2014 1:42 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:31 AM
Points: 40,177, Visits: 36,578
GilaMonster (4/11/2011)
Please post new questions in a new thread. Thank you.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1612374
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse