Reporting Views and Summary Tables Design
Make reports fast and consistent without duplicating logic.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design reporting structures. Source tables: [SOURCE_TABLES]. Reports needed: [REPORTS]. Refresh frequency: [REFRESH_FREQUENCY]. Users: [REPORT_USERS]. Propose views for common joins and calculations, with definitions of each metric written once, such as active customer or monthly revenue. Propose summary tables where views are too slow, with their refresh method and a check that totals match the source. Return the definitions, the SQL for two views, a reconciliation query, a naming convention and a note on access control for sensitive columns. List metric definitions that stakeholders should approve, since disagreements about definitions cause more trouble than slow queries. Add guidance on versioning definitions: when a metric definition changes, record the date and keep the old definition available so historical reports can be explained. Provide a worked example of two stakeholders defining active customer differently, and show the two queries and the difference in numbers using invented figures. Suggest a monthly review where owners confirm definitions and a place to document them.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.