|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 11:37 AM
Points: 2,551,
Visits: 7,201
|
|
Regardless of your current problem, if 'Aquapak_Live_app' database is a critical database, then you most likely should have it in FULL recovery, and take regular trans log backups so you can recover to point in time.
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: 2 days ago @ 9:23 PM
Points: 312,
Visits: 1,856
|
|
Ausman,
Just changing the recovery model to simple does not truncate the log....I think it has to wait for the next checkpoint to happen.
Also, I have noticed that if you haven't done log backup in a while and if the log is big, you have to do log backup couple of times and then shrink the log in order to free up space.
Please let u know how it went.
Thanks, SueTons.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, February 22, 2013 1:42 PM
Points: 5,
Visits: 9
|
|
You guys are right so i have contacted SAGE about this and they said that the DB should have been in Bulk logged mode but someone went in there before me and changed it to Simple for whatever reason.
I will sometime today backup the DB and change it to Bulk Logged Turn on Transaction log backups for it and let them run every half hour
Thank you so much guys :)
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Yesterday @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
Bulk logged is not usually an isolation level that's used for long periods of time, because of the risks involved (can't do point in time recovery to a log interval that contains a bulk operation). Since the point of log backups is to allow point in time recovery, that's kinda counter-productive.
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
|
|
|
|