How Can We Help?
Answer
- Create a SQL Job that runs the “xmi_Update” stored procedure located in the Data Warehouse database.
- Recommendations
- Create the Job to run the update overnight (“xmi_Update” stored procedure) on the Data Warehouse.
- If more frequent updates are required, for example, update every 15 minutes, monitor the SQL Server to ensure there is no excessive load that could have a negative impact on other systems using the SQL server.
- The first run of the data warehouse update on a pre-existing XMPro database could take many hours to complete. Please take this into consideration when scheduling the first update.
- After the stored procedure has run for the first time amend the “xmi_Update” stored procedure and comment out the command
“exec xmi_SchemaRemoveCustomTables”.
- “xmi_Update” stored procedure structure:
- The following commands are responsible for updating the data warehouse data from the XMPro Core Database
- exec xmi_BatchUpdateTransactionLog
- exec xmi_BatchUpdateTransactionValue
- exec xmi_SetLastTaskID
- When major changes to the XMPro Processes/Activities are made, it is recommended that the “exec xmi_SchemaRemoveCustomTables” command is run.
Note: At all other times, this command should not be run. - The command “exec xmi_SchemaRefresh” will amend any changes to tables or create any new custom tables.
- The command “exec xmi_BatchUpdateCustomTables” will populate the custom tables created by the “xmi_SchemaRefresh” stored procedure above.Note: The custom tables are based off of the processes and activities that have been developed/created in the XMPro core database.
- The following commands are responsible for updating the data warehouse data from the XMPro Core Database
Comments are closed.