Why 1C reports are slow and how to move analytics to a separate database

Why it happens

• The 1C database is optimized for posting documents, not for large multi-year queries.
• A yearly report reads millions of register rows and locks tables people work with.
• Every user builds their own reports — the load adds up.

The fix: accounting and analytics apart

The tables you need are copied into a separate SQL database, and all reports run there. 1C only hands over changes — a few seconds — and is free again.

1. Install ETL Sync and connect the 1C database with a read-only login.
2. Pick tables: sales documents, stock and sales registers, catalogs.
3. Use "changes only" for documents and "by recorder" for registers.
4. Set a quiet window: light refreshes in working hours, heavy ones at night.
5. Connect Power BI or Excel to the warehouse.

What you get

• Yearly reports in seconds instead of minutes.
• 1C stops freezing for accounting.
• Data from several 1C bases and BILLZ in one place.