Detecting risky SQL and enforcing SQL standards

By enforcing SQL Assurance rules, you can identify problematic SQL statements early in the development lifecycle. This reduces the likelihood of performance issues in production and supports shift-left practices in mainframe DevOps.

The benefits include:

• Performance issues are caught early, reducing production incidents
• Application developers receive immediate feedback on SQL quality
• CI/CD pipelines enforce SQL standards automatically
• Compliance and audit readiness are improved

Workflow for detecting risky SQL and enforcing SQL standards

Task	Product	Role	Action	Reference
1	Time Sharing Option/Extension editor (TSO/E editor)	Db2 DBA	Copy sample SQL rule set and define your custom SQL rule set to use in the SQL evaluation	Customizing expert rules
2	Jenkins, Azure DevOps, GitHub Actions, or GitLab CI/CD	CI/CD Pipeline Engineer	Configure project or pipeline to trigger SQL evaluation	Quick start to SQL Risk Detection
3	BMC AMI SQL Assurance for Db2	Application Developer	Define SQL input details for evaluation	Using Jenkins UI or UC YAML configuration and pipeline files: Jenkins: Configuring the project Universal Connector: Creating a configuration file Select applicable configuring topic: Configuring the Azure DevOps pipeline Configuring the GitHub Actions workflow Configuring the GitLab CI/CD pipeline
4	BMC AMI SQL Assurance for Db2	Application Developer	Review project or pipeline console log results	Reviewing project/pipeline results: Jenkins: Building the project and reviewing its output Universal Connector: Running the pipeline and workflow and reviewing its output
5	BMC AMI SQL Assurance for Db2 or BMC AMI Command Center for Db2	Application Developer, Db2 DBA	Review SQL rule violations in SQL Assurance report or Command Center Violations view	Reviewing SQL violations: Sample SQL Assurance report (AS$RSLT) Viewing expert rule violations