What happens when my database schema changes in iDBQuery?

Databases evolve: a team adds a column, renames a table, or introduces a new dimension. iDBQuery is built to keep up rather than break.

• Re-introspection. iDBQuery can refresh its map of a source, detecting new tables and columns and updated types, so its understanding matches the live schema.
• Definitions persist. The meanings, synonyms, metrics, and relationships you've recorded in the semantic layer and business glossary carry across, so a schema refresh doesn't wipe the knowledge you've built up.
• Graceful handling. If a question references something that has moved or been removed, iDBQuery surfaces that clearly — and its query self-correction helps it adapt to structural changes rather than returning a confusing error.

This matters because the alternative — hand-written reports and dashboards that silently break when a column is renamed — is a familiar maintenance burden. Since iDBQuery generates SQL fresh for each question against the current schema, there are far fewer brittle, hard-coded queries to fix. And because every answer shows its SQL and cites source rows, you can immediately see whether it's using the new structure, giving you confidence that reporting stays correct through change.