Deployment planning considerations for customizations
Before you deploy a customization, review any dependencies between customization packages and any database schema changes that are included in the deployment. These conditions can affect deployment order, scheduling, and deployment success.
Customization dependencies
If dependencies exist between customization packages, determine the order in which to deploy the packages. For example, if you deploy both an IBM Sterling® Order Management System package and a IBM® Sterling™ Call Center package, determine which package must be deployed first based on the dependency requirements of your implementation.
Database schema changes and deployment scheduling
Some database schema changes require Db2® table reorganization after the ALTER statement runs. If a deployment that includes these schema changes runs at the same time as scheduled database maintenance activities, such as backups, the deployment process might conflict with maintenance operations and fail.
The following schema changes do not require table reorganization and can be deployed while scheduled database maintenance activities are running:
- Add a primary key constraint.
- Mark a table as volatile.
- Add a column.
- Increase or decrease a column size.
- Change or set a column default value.
- Drop a column.
- Change a column data type.
- Change a column from not null to nullable.
- Change a column from nullable to not null.
If your customization includes schema changes that require table reorganization, schedule the deployment outside of the maintenance window that is used for database maintenance activities.