The transaction log for the WF database being full due to 'LOG_Backup'

replied on November 8, 2016

Hi Sheyla.

01 You should first do a backup of your database before to the shrink of the workflow database.
02 After this I suggest you change the recovery model to simple
03 Just to be sure monitor your workflow looking for any runaway workflow that could be a reason for you log size.
04 And review the size of your log the average size of your log should be 10% of your database if the top size are too small you should considere increment the size.
05 Do periodically backups of you database that also prevent an increment your log size.

Hope this work for you Regards!!

0 0

View 2 previous replies

replied on November 8, 2016

I wouldn't recommend putting the Workflow database in simple recovery mode because that makes it more likely you'll have inconsistencies between the Workflow database and the repository should you ever need to recover from backup.

0 0

replied on November 8, 2016

Thanks!! Miruna I will consider not use the simple recovery mode.

0 0

replied on November 8, 2016

Yes the workflow database was shrunk. However, is there any way to automate the shrink process?

Can you please tell me how point 4 should be checked? "review the size of your log the average size of your log should be 10% of your database if the top size are too small you should considere increment the size." What do you mean by top size and how to increment the size?

0 0

replied on November 9, 2016

Hi Sure Sheila.

In SQL Management studio there are options to see the top size.
To resume I attach a video where I show you how to do it

SQLServer.mp4 (2.75 MB)

0 0

replied on November 9, 2016

Hi Sheila.

About to automate process I think that maybe using a custom query with a Backup and Shrink files by Script on it in a workflow with certain shedule can work for you.

0 0

Question

Question

The transaction log for the WF database being full due to 'LOG_Backup'

Replies

Sign in to reply to this post.