What SqlDBM Copilot can do with Excel export and import
SqlDBM Copilot can build and read Excel workbooks to fit them into your modeling workflow. Here are the practical ways to use it.
Exporting to Excel
Getting your model out in a format your whole team can read and work with.
- Documentation and review packages. SqlDBM Copilot can produce a data dictionary for stakeholder review, your tables, columns, data types, descriptions, and ownership, plus a relationship catalog and column lineage, and a gap-analysis sheet that flags anything undocumented.
- Governance and compliance reports. SqlDBM Copilot can generate audit-ready exports: what's flagged as sensitive, how data is classified by schema, ownership and stewardship assignments, and anything missing descriptions or governance metadata.
- Impact analysis before a change. SqlDBM Copilot can show what depends on a table, downstream consumers, column usage across views, and relationship maps, so refactoring is planned, not discovered.
- Quality and health checks. SqlDBM Copilot can surface tables missing primary keys, orphaned tables with no relationships, documentation coverage, and naming inconsistencies in one workbook.
Importing from Excel
The fast way to bring information back in, especially when other people are contributing.
- Bulk metadata enrichment. SqlDBM Copilot can take a template your business experts fill in, descriptions, ownership, classification levels, business rules, and import their updates straight back into the model. No SqlDBM access required on their end.
- Migration from other sources. SqlDBM Copilot can import existing data dictionaries, create tables from spreadsheet schemas, and port relationship definitions rather than rebuilding by hand.
- Standardization at scale. SqlDBM Copilot can apply consistent data types across many tables in one pass, fix naming, assign tags in bulk, and attach column templates to table groups.
- Offline collaboration. SqlDBM Copilot can export a slice of the model for a contractor or partner team, then import their proposed tables and columns after you review them.
Where to start with your project
You've got one error and one warning showing, so a good first step is a validation export, SqlDBM Copilot can lay out the error and warning details, every table's status, and anything missing a primary key or documentation.
From there, exporting your Account Master diagram with its columns, keys, relationships, and current documentation status gives you a clean working picture of that area.
Just tell SqlDBM Copilot which one you'd like, and it will build it.