Why does the log grow quickly if WF_INSTANCE_SAVE is “ALWAYS”?


Why does the Microsoft SQL Server transaction log file get too big quickly if WF_INSTANCE_SAVE is set to “ALWAYS” on the IBM TRIRIGA product? We have set WF_INSTANCE_SAVE to “ALWAYS” in the TRIRIGAWEB.properties file, and we see the Microsoft SQL Server transaction log file getting too big really quickly, until it consumes all available disk space on the database server. Why does this happen?

When you set WF_INSTANCE_SAVE to “ALWAYS” in the TRIRIGAWEB.properties file, the code will start recording all workflow actions and details in specific tracing log BOs/tables in TRIRIGA. This will drastically increase the database activity due to all of the inserts in this tracing table, and the MS SQL Server Transaction log file will quickly start getting bigger and bigger as time goes by, until you may run into a lack of disk space on the database server.

Our IBM TRIRIGA Best Practice for System Performance [PDF] document does not recommend you to set WF_INSTANCE_SAVE to “ALWAYS” in the TRIRIGAWEB.properties file at all. This property needs to be set to “ERRORS ONLY” to reduce the database activity regarding any tracing information from workflow runs.

[Admin: This post is related to the 08.26.14 post and 11.06.14 post about performance best practices.]

Continue reading

One thought on “Why does the log grow quickly if WF_INSTANCE_SAVE is “ALWAYS”?

  1. Pingback: How can you diagnose memory issues in TRIRIGA servers? | TRIRIGAFEEDIA

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s