jjlbmcnews
IS-IT--Management
Guys and Girls,
I have various maintenance tasks that run during the very small period of inactivity that occurs on our database (we're a 24 hour operation). I have noticed that the transaction log dumps after maintenance are huge, we're talking gigabytes, this is becoming hard to manage in terms of backups. The database recovery model has been set to full, which I understand logs all activity hence the size of the log dumps after the maintenance has finished. What I was thinking of doing was changing the recovery model on the fly so before the first routine starts change the recovery model to simple, then once routines are finished change the model back to full, when data entry and manipulation starts, how does that sound?
I have various maintenance tasks that run during the very small period of inactivity that occurs on our database (we're a 24 hour operation). I have noticed that the transaction log dumps after maintenance are huge, we're talking gigabytes, this is becoming hard to manage in terms of backups. The database recovery model has been set to full, which I understand logs all activity hence the size of the log dumps after the maintenance has finished. What I was thinking of doing was changing the recovery model on the fly so before the first routine starts change the recovery model to simple, then once routines are finished change the model back to full, when data entry and manipulation starts, how does that sound?
