This tool has been designed to provide near real-time validation of the naming standards for Data Quality (IDQ) transformations, mappings, mapplets, workflows and applications. The automated code review process helps eliminate human error, streamline code reviews and help enforce consistency across the team’s code base.
The initial setup of this tool is straight forward since no new technologies are introduced. All the code used for the validation is done on the database level which the team often already has access to. A set of tables and stored procedures are installed on the existing database server housing the Informatica repository databases. The team lead defines the naming standards for the IDQ Objects.
After the initial setup is complete, using the tool for validation is simple. When a developer wants to validate their code, they execute a database stored procedure (SP) with the IDQ Application name and DIS name as parameters. The tool then takes care of the rest. In near real time the SP returns a result showing any code violations found in the IDQ Objects. The team does not need to perform any manual steps of importing or exporting code for the validation to take place. The SP response time can vary depending on the team’s database setup but results are often shown in less than one minute.
The Binary Bolt, LLC Azure SQL platform has a 99.99% uptime SLA. Data at rest in Azure SQL is fully encrypted. All communication with Azure SQL is also encrypted with TLS version 1.2 or greater. Data is additionally secured by logins, passwords and firewalls which only allow access to the data from pre-approved IP addresses.
IDQ Level:
Creates mappings, mapplets, transformations and workflow objects.
Deploys these objects as an IDQ application.
Database Level:
Executes the Binary Bolt validation Stored Procedure (SP).
Includes the Application and DIS Name as a parameter to the SP.
In near real time the SP returns back a report to the developer with any validation issues found.
When the SP is called, it gathers any information it needs from the IDQ repository tables. The information is securely sent to the Binary Bolt's Azure database instance for processing. Azure SQL responds back to the developer with the results in the SP.
The developer creates an IDQ workflow, mapping and then deploys it as an application named app_wf_Flat_File.
The Developer runs the Validation SP application app_wf_Flat_File.
The developer reviews the Validation SP results and notes the objects names that need to be corrected in the mapping and workflow.
The developer corrects the issues in the mapping and workflow and redeploys application app_wf_Flat_File.
The developer reruns the Validation SP and verifies all the issues have been corrected successfully.