SQL Standardize

Standards Enforcement

Enforce naming conventions, coding standards, normalization rules, and best practices across all your SQL Server and PostgreSQL database objects.

What Gets Standardized

Naming Conventions

Table prefixes/suffixes
Column naming patterns
Index naming
Constraint naming

Coding Standards

Consistent formatting
Comment requirements
Error handling patterns
Transaction patterns

Object Selection

View vs Table decisions
Function vs SP guidance
Table types vs Variables
Trigger appropriateness

Data Types

Appropriate type selection
Size optimization
Nullable consistency
Default value patterns

Normalization

1NF through BCNF checks
Denormalization justification
Redundancy detection
Dependency analysis

Security

Permission patterns
Schema separation
Dynamic SQL safety
Injection prevention

Configurable Rules

Define your organization's standards in a simple YAML configuration

# sql2ai-standards.yaml
naming:
  tables:
    pattern: "^[A-Z][a-zA-Z]+$"  # PascalCase
    prefix: null
    suffix: null

  columns:
    pattern: "^[A-Z][a-zA-Z]+$"
    primary_key: "{Table}Id"
    foreign_key: "{ReferencedTable}Id"

  indexes:
    pattern: "IX_{Table}_{Columns}"
    unique: "UX_{Table}_{Columns}"

  stored_procedures:
    pattern: "^(Get|Set|Insert|Update|Delete|Process)[A-Z]"

coding:
  require_try_catch: true
  require_transaction: "for_modifications"
  max_procedure_length: 500
  require_comments: "public_objects"

normalization:
  minimum_form: "3NF"
  allow_denormalization: "with_justification"

Sample Scan Results

SQL Standardize Scan Results
════════════════════════════════════════════════════════════

Database: ProductionDB
Scanned: 156 tables, 89 procedures, 45 views, 23 functions

NAMING VIOLATIONS (47 found)
────────────────────────────────────────────────────────────
⚠ Table 'tbl_customers' → Should be 'Customers' (no prefix)
⚠ Column 'cust_id' → Should be 'CustomerId' (PascalCase)
⚠ Index 'idx1' → Should be 'IX_Customers_Email' (descriptive)
⚠ Procedure 'sp_GetData' → Should be 'GetCustomerData' (no sp_)

CODING VIOLATIONS (23 found)
────────────────────────────────────────────────────────────
✗ Procedure 'UpdateInventory' missing TRY/CATCH
✗ Procedure 'ProcessOrders' has 847 lines (max: 500)
✗ Function 'fn_Calculate' uses dynamic SQL (security risk)

NORMALIZATION ISSUES (8 found)
────────────────────────────────────────────────────────────
⚠ Table 'Orders' has repeating group in columns 'Item1-Item10'
⚠ Table 'Customers' has transitive dependency: City → State

[Generate Fix Script] [Export Report] [Configure Rules]

CI/CD Integration

Block deployments that violate standards before they reach production

🔄

Pre-Commit Hooks

Check standards before code is committed

🚀

Pipeline Gates

Fail builds that violate standards

📊

PR Comments

Automated review comments on violations

Enforce Your Standards

Consistent naming, coding conventions, and best practices across all your databases.

Start Free Trial View All Features

No credit card required • Free for individual developers