Asynchronous Promotion Processing
By default, Prospect2 processes and updates Promotion records in Tessitura in real time. For large organizations or organizations with regular large deployments, an organization may choose to have those records processed asynchronously (not in real time) in an effort to minimize the impact of processing on the database. To enable the Asynchronous Promotion feature of Prospect2, follow the steps outlined below.
Before you begin, make sure that you've installed the most recent version of the Prospect2 install script that is compatible with your version of Tessitura.
Consortium Organizations
Since each organization has their own set of Prospect2 settings in T_DEFAULTS, this feature can be enabled/disabled as needed for each organization independently from each other. You only need to schedule LT_PRO2_PROMOTION_LOG once for the entire consortium, however, as it will pick up all Promotions that need to be updated and update them appropriately each time that it runs.
Any organizations that has P2UpdatePromoInBulk set to NO will still have their Promotions in Tessitura updated in real time.
Set "P2UpdatePromoInBulk" to "YES"
In T_DEFAULTS, set P2UpdatePromoInBulk to YES for each parent table used by Prospect2 that would like to take advantage of Asynchronous Promotion Processing. This will cause all Promotion messages from Prospect2 to immediately begin inserting to LT_PRO2_PROMOTION_UPDATE, instead of being processed real time.
Verify That These Objects Exist in Your Database
- LP_P2_UPDATE_PROMOTIONS_IN_BULK
- LT_PRO2_PROMOTION_UPDATE
- LT_PRO2_PROMOTION_LOG
Create a Database Routine
Create a scheduled database routine in SQL Server Management Studio that executes LP_P2_UPDATE_PROMOTIONS_IN_BULK. This routine may be run as often as you'd like. We recommend having it execute at least once per day, or as often as every minute. It depends on your organization’s needs. LP_P2_UPDATE_PROMOTIONS_IN_BULK takes care of processing any Promotions that are stored the the LT_PRO2_PROMOTION_UPDATE table.
The SQL job you created will then pick up the records and process them on the schedule you defined for the routine. After being processed, all rows processed by the job are moved to the LT_PRO2_PROMOTION_LOG table, where they will remain for 3 months. Each time the LP_P2_UPDATE_PROMOTIONS_IN_BULK procedure runs, it will remove any logged messages older than 3 months to prevent the table from growing too large.