With Prompt's SQL Code Analysis, you can:

• Prevent the build-up of technical debt in your database code – spot immediately issues that could eventually cause problems with performance, behavior, or security.
• Minimize delays in deployment – these are inevitable if code issues are detected only at deployment time, when a DBA reviews the code manually
• Reduce maintenance costs –often reported as accounting for between 60-90% of the total application lifecycle costs. For the database, this means significantly less time spent diagnosing erratic or slow performance, or resource contention issues, such as blocking, or fixing data integrity issues, or security problems.

SQL Prompt's built-in static code analysis rules allow teams to check for problems automatically, during development and testing work, therefore minimizing the number of 'code smells' that creep into the application and database builds and improving build reliability.

Static code analysis parses the source code, checking the syntax for compliance with a built-in set of rules. These rules are designed to encourage good coding practices, and to alert the team to possible mistakes, omissions and vulnerabilities in the code base. Issues detected include problems with table design, such as a missing clustered index, or naming problems, such as use of reserved words, or problems with query logic that could cause unpredictable performance or behavior, or even cause security problems.

See: SQL Code Analysis