Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Super Bronze

Unity - SQL - Simple / Full Recovery Methods


I've come accross a few problems with Unity servers where the SQL transaction log for the UnityDB grows until it fills the disk and starts causing problems (i.e. 7gb+).

As I have some background in SQL it's easy enough to fix... but I've seen this post:

It states we need Full recovery model, or the 'nightly truncates' will fail. If they do fail, surely this can be ignored as truncations are not required with the Simple recover model?

Anyone any other reason full recovery would be required? The difference AFAIK is that with simple, the transaction log is cycled and therefore kept small.

With full, it is written to, and can grow, and the log is only truncated/reused after a full backup.

If, therefore, our customers don't back up their DB regularly (and we all know they don't!) they get this problem... eventually it grows.

Why would full recovery be required when even if we did a full system restore we wouldn't likely do a transaction log restore, as we have a full DB backup taken at the point the whole system was backed up?



Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

Re: Unity - SQL - Simple / Full Recovery Methods

Aaron This is not an answer to your question However you might want to look at following Bug

Also a Microsoft document that answers exactly that question as to why it grew so large. Again, this document applies to any applications that uses MS SQL as its backend database.

Here is the comprehensive doc about SQL server maintenance.;en-us;873235