Mapping an old data warehouse
DB Explorer makes a decades-old data warehouse understandable from its schema export, without a single row of data: layers, data lineage, business names and risks, with evidence.
What the video says
DB Explorer is the database module of Legacy Explorer. It makes old databases and data warehouses understandable from their schema export, without a single row of data. In a decades-old data warehouse, the business logic is scattered: across stored procedures, load processes and reports.
This example has 755 tables and 293 procedures, and the documentation stopped keeping up with them long ago. From this, the structural map is ready in seconds: which layer loads from which, what calls what, and where the data flows. This is automated processing without artificial intelligence, so the same export always gives the same result.
The load processes show the data lineage: what a table is built from, and what builds on it. Click a procedure to see what it reads, writes and calls, along the full call chain. This answers the most common question: what is affected if we touch it?
Tables get a business name and a short description, and columns get a glossary. In-house abbreviations, however, are something a machine cannot know. In one test, none of 36 tables got the right name on the first try, without an explanation.
With a three-line explanation, 35 did. It also shows what is not needed: orphan tables, objects nothing writes to, dynamic SQL. With evidence, and with what the exploration could not see marked separately.
For procedures we see not only what they read, write and call, but also what they do: what they load, from where, and by which rule. It interprets load processes and report outputs, such as Power BI reports, the same way. It also follows the data at column level, and recognizes overlapping tables with a similar structure.
The result can be explored in a browser, exported to Excel and Markdown, and through MCP it can be the context of any AI assistant. The system runs in your own environment: it sees column names, not data values. Up to date, provable, secure: even an old database becomes understandable before anyone touches it.
This is DB Explorer, part of Legacy Explorer.
