Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-5404

Verify integrity of database schema at server startup

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Database
    • Labels:
      None
    • Edition:
      Community

      Description

      Database-related errors are sometimes misleading and hard to investigate. The fail-fast approach consists to verify database integrity at server startup. It should improve troubleshooting of these problems.

      To be verified

      • missing table (can it really occurs ??)
      • missing index
      • index is not correct (columns and/or uniqueness)
      • missing columns
      • too many columns
      • nullability of column
      • InnoDB tables on MySQL
      • too many indices
      • charset and case-sensitivity
      • column type
      • max length of varchar columns

      Nice-to-have, no need to be verified in the first version

      • too many tables in the schema (would it be valuable ? it does not have side-effects)
      • oracle sequences and triggers
      • value of oracle sequence > max(id)

      A boolean parameter should allow to ignore the errors raised during integrity verification. In any case they should be logged in sonar.log. The value of this parameter must be displayed in the page System Info.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              simon.brandhof Simon Brandhof (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: