Reports and dashboards straight from SQL Server.
If your ERP, accounting, or operations system keeps its data in Microsoft SQL Server, Tau connects with one read-only login and gives you dashboards, printed reports with page numbers, matrices, drill-through, and scheduled delivery, with an assistant that writes the SQL.
Where SQL Server reporting is stuck.
The data is right there, in tables you can already query, and the tools to report on it have not kept up. SSRS still works and still looks and feels like 2008; Report Builder is awkward for anyone but a developer, and the web portal is not somewhere people want to spend time. Crystal Reports built half the printed documents in mid-market business and is now something companies are trying to leave, not start with.
Power BI is a strong analysis tool and a poor printing tool: paginated reports need Premium or per-user Premium licensing, a separate designer, and a separate skill set. The ERP's own report writer covers its own tables and nothing next to them.
So the pattern in most SQL Server shops is views written by one person, queried from Excel by everyone else, and emailed by hand.
What Tau reads from SQL Server, honestly.
Tau connects to Microsoft SQL Server directly: on-premises, in a VM, or Azure SQL, with a read-only login that IT creates and controls. Add as many databases as you have; a single report can join the ERP database to the warehouse management system and a spreadsheet import in the same query. Nothing is copied unless you want it to be.
Business Central and other OData V4 sources join the same reports through a local mirror that Tau keeps in sync by polling every minute and, when Tau has an HTTPS address, by webhooks. Everything Tau builds sits on top of ordinary SQL you can read, keep, and version.
Runs on your server. One service on Windows or Linux, or a container. A read-only login. Reports are plain files with version history. Nothing leaves your network unless you schedule a delivery.
Reports SQL Server teams build first.
The demo runs on Northstar Coffee, an invented company in a real database. It shows the same report types below on sample data, not on SQL Server.
Aged trial balance
Grouped by region and customer with aging buckets, running totals, and page N of M on Letter landscape, delivered as a PDF at month end.
See this report type in the demo →Executive dashboard
Revenue KPIs, a multi-year trend, category mix, a region treemap, and top customers, with filters that narrow every visual and a drill to the orders.
See this report type in the demo →Sales matrix
Product categories down the side, months or regions across the top, amount and margin in each cell, exported to Excel with live formulas.
See this report type in the demo →Fulfillment dashboard
On-time delivery, days to ship, an orders-to-cash funnel, and a backordered orders table with a right-click drill to the lines.
See this report type in the demo →Tau and SQL Server: the questions we get asked.
Which SQL Server versions and editions work?
Any supported SQL Server, including Express, Standard, Enterprise, and Azure SQL Database. Tau uses a standard read-only login; no agent or extension is installed on the database server.
Does Tau copy my data anywhere?
Not for SQL Server. Queries run against your database when a report opens or a delivery runs. Only OData sources such as Business Central are mirrored locally, and that mirror lives on the server you run Tau on.
Can Tau replace SSRS or Crystal Reports?
For paginated reports built from queries, yes: report, page, group, and detail bands, running totals, subreports, and page numbers, designed in the browser and delivered by email on a schedule.
See it on your SQL Server data.
Tell us how you run SQL Server and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.