Menu

Self-service reporting without hurting your production database: replicas, views, indexes and timeouts
📰

Self-service reporting without hurting your production database: replicas, views, indexes and timeouts

DEV Community: dotnet·Razi Syed·6 days ago
#Cg71wfVB
#devtodotnet#devto#dev#reporting#report
Reading 0:00
15s threshold

By Razi Syed. Sample code: github.com/dotnetreport/dotnetreport

You ship self-service reporting, people love it, and three weeks later someone in ops asks why checkout got slow every weekday at 9 a.m. The answer is usually a finance user running "all orders, all time, grouped by customer" against the same database your app writes to, then exporting it to Excel. Twice.

Ad hoc reporting changes who writes your queries. Before, every query against production went through code review. Now the person composing a query is a user clicking columns together, and they have no idea which table has 40 million rows. You can't review those queries, so you have to make the environment safe for them instead.

This post is the checklist I use, with the specifics of how Dotnet Report (which I work on — disclosure) talks to your database, because you can't tune a workload you don't understand.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.