You are viewing limited content. For full access, please sign in.

Question

Question

How to mitigate DB transaction log growth for bulk workflows?

Workflow
Updated January 29, 2014
asked on January 25, 2014

The issue I have is that we sometimes have "maintenance" workflows that need to run on large numbers of documents. This usually ends up with the SQL transaction log for the Workflow database running itself out of space.

 

On the Advanced Server Options>Workflow tab I've unchecked all of the tracking options except for warnings and errors for this particular workflow. Will this slow down the growth of the transaction log, or is there something else I could be doing?

1 0

Answer

APPROVED ANSWER
replied on January 27, 2014 • Show version history

Hi Devin,

 

Have you tried setting the recovery model of the Workflow database to "Simple"? If you're not taking log snapshots and are only performing one full backup per day, then just leave it as "Simple." Otherwise you may need to consider a window to run the maintanance windows when the database has been temporarily switched to "Simple."

 

See:

http://msdn.microsoft.com/en-us/library/ms189275.aspx

 

-Ben

 

1 0
replied on January 29, 2014

Thanks. We ended up creating a log backup that runs every hour.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...