Skip to content
← All work

Reporting & Analytics

RTH Utility SQL Analyzer

In design — exploratory

A Windows desktop workbench, in early design, intended to turn SQL Server and SSRS assets into a structured, reviewable reporting knowledge base. It would collect report definitions, dataset SQL, schema and dependencies, and keep facts, inferences and human decisions apart.

Understanding a large SSRS estate means answering questions such as which reports use a given table or filter, and where two similar reports differ in meaning. The product intent is a trustworthy repository of report files, extracted SQL, schema and human-reviewed business rules that those questions can be asked of.

What it solves

  • Finding every report and dataset that touches a given table, column or filter.
  • Spotting meaningful differences between related reports: joins, filters, date logic and aggregation.
  • Recording what a metric means, and checking whether reports agree with it.

Technology stack

C# / .NETWPFMicrosoft ScriptDOMSQLite

My role

I am defining the product and its governance, with a first end-to-end slice planned before the application is built. The technology choices are working hypotheses and may change.

Highlights

Deterministic first

Parsers, rules and tests establish findings. AI is planned later as a way to retrieve and explain evidence, not as the authority for facts.

Preserve originals

Imported report files are immutable and always traceable, and the workspace is stored as readable, Git-friendly files with SQLite for indexing.

Visible uncertainty

Unresolved references and unknown business meaning become explicit review questions rather than guesses.

Key decisions

Read-only by default

Early versions collect metadata and code without changing production systems or importing business data.

Build one vertical slice first

The first release completes one useful workflow end to end before the scope broadens.

Status

The repository is in its first phase, product definition and development governance. It is an exploratory internal utility and is not production software.

Have a similar problem to solve?
Let’s talk about what a practical solution would look like for your organization.
Discuss a project