Quick publish performance tuning
Aside from publishing workspace data to the Production environment database, quick publish also updates and marks all corresponding data in the production-ready schema STAGLOG table as processed. This ensures that the data that is being quick published to the production database are not processed and published again during the next iteration of stagingprop. This process can take a long time to complete. If your database configuration meets certain criteria, you can tune the performance of quick publish by setting two optional attributes.
About this task
- lowerCaseStaglog – Determines how the quick publish converts
string characters in custom staged tables. This attribute can have
two possible values:
false
(default) – SQL statement uses LOWER() to convert all string characters in custom staged tables to lowercasetrue
– Removes LOWER() from the SQL statement, thus improving performance. You can set lowerCaseStaglog totrue
when one of the following conditions are met:- There are no custom stageable tables in the schema
- All UPDATE, DELETE, and INSERT triggers on all custom stageable tables insert lowercase values only into the STGTABLE column of the STAGLOG table.
- updateStaglogStmtNum – Determines how the quick publish
updates the STAGLOG table. This attribute can have two possible values:
0
(default) – Uses an EXISTS clause in the SQL1
– Uses an IN clause in the SQL; improving performance. However, if you have already fine-tuned the performance of your database, performance might not improve.
Procedure
To tune quick publish performance: