Best practices for BMC AMI SQL Assurance

We recommend that you review best practices for the BMC AMI SQL Assurance for Db2 product before implementing a product or a feature. 

Set up your system to avoid future rework

Best practice
Establish a standardized CI/CD pipeline for Db2 SQL evaluation early in your DevOps adoption. Use version control for all scripts, define clear naming conventions and folder structures. This minimizes rework and simplifies onboarding for new team members.

Use environment-specific configurations

Best practice
Run SQL analysis with environment-specific metadata (for example, DEV, QA, or PROD) and use separate configuration files for each environment. This supports smoother transitions between stages.

Integrate with DevOps pipelines for proactive SQL analysis

Best practice
Implement SQL Assurance checks into CI/CD pipeline/workflows. Analyze SQL statements for static and dynamic SQL in each Db2 environment to catch inefficiencies early. This reduces production issues and aligns SQL performance with application delivery cycles.

Monitor and audit SQL risks

Best practice
Use console logs to monitor SQL analysis and generate reports to identify SQL risk and rule violations. Share insights with stakeholders to support compliance, capacity planning, and continuous improvement.