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 «««123

Backup Log cannot be performed because there is no current database backup Expand / Collapse
Author
Message
Posted Monday, April 8, 2013 7:46 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: Yesterday @ 3:43 PM
Points: 43,047, Visits: 36,206
So the full backup is reinitialising the log chain and hence the log backups run. It's not a good maintenance schedule though. Switching to simple recovery for index rebuilds is not going to do good things to your ability to restore to a point in time (which I assume is why the DB is in full recovery).


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 #1439833
Posted Monday, April 8, 2013 7:51 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, August 28, 2014 1:11 PM
Points: 23, Visits: 187
I completely agree with you. I am not sure why they did that to begin with I will create a new optimization job later, but for right now I have to stop it because I need those Tran jobs to run. It's critical!
Post #1439839
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse