Enforcing schema standards during deployment
Related topics
By enforcing Schema Standards rules, you can maintain data integrity, performance, and compliance with BMC AMI DevOps for Db2.
The benefits include:
- Schema changes are validated before deployment.
- Violations are flagged early, reducing risk.
- Data integrity and performance are preserved.
- Governance and audit readiness are strengthened.
Workflow for enforcing schema standards
| Task | Product | Role | Action | Reference |
|---|---|---|---|---|
| 1 | BMC AMI Command Center for Db2 | Db2 DBA | Create a Schema Standards rule set and rules for organization's schema requirements | Quick start to automating Db2 schema changes |
| 2 | BMC AMI DevOps for Db2 | Application developer | Submit schema changes via the CI/CD project or pipeline | Quick start to automating Db2 schema changes |
| 3 | BMC AMI DevOps for Db2 | Application developer, Db2 DBA | Define the schema source and submit schema standards validation | Schema standards configuration:
|
| 4 | BMC AMI DevOps for Db2 or BMC AMI Command Center for Db2 | Application developer, Db2 DBA | Review schema standards violations in the Schema Standards report or Command Center Violations view | Monitoring schema standards: |
| 5 | BMC AMI DevOps for Db2 | Application developer | Correct schema violations and submit the Schema Standards step via the CI/CD project or pipeline | Schema standards configuration:
|
| 6 | BMC AMI DevOps for Db2 | Application developer | When violations are resolved, submit JCL via the CI/CD tool to apply schema changes | Running JCL:
|
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*