1. Optimized performance for BG VAT Declarations with large data sets
Time to announce significant performance improvements for processing BG VAT Declarations, especially when handling large data sets with hundreds of thousands of records.
Previously, users experienced long processing times when working with extensive VAT declaration data. To address this, we optimized the system on multiple levels, ensuring faster and more efficient operations.
Key Optimizations
✅ Performance Improvements – We fine-tuned several critical requests, resulting in significant speed improvements in the calculation of:
- VAT Declaration's totals – 1.5x faster
- Sales Ledger – 1.4x faster
- VIES Declaration Lines – 9x faster
- VIES Declaration – 8x faster
✅ New Feature: Export VAT Files via Navigator
We have added the ability to start VAT file exports directly from the Navigator using the Create VAT Files function.
Previously, exporting required opening the specific VAT declaration and running the function inside the document, which added unnecessary load to the process. Now, with just one click from the Navigator, the system reloads all data automatically — reducing processing time and improving performance for large databases.
The Result?
Processing BG VAT Declarations is now significantly faster, more reliable, and better optimized for large data volumes.
These improvements reflect our ongoing commitment to enhancing system performance and user experience. If you have any questions, feel free to reach out to our support team.
2. Smarter Server Telemetry: Daily Trends & 5-Minute Performance Snapshots
We’ve introduced smarter, hands-off server telemetry that continuously tracks core load and data growth—no manual work needed.
Daily table size tracking
Every day, the system records the size and row count of all tables. You get clear growth trends for capacity planning and housekeeping.
-
Where users see it: Navigator → Instance Statistics (read-only).
-
Stored in: local DB table Sys_Instance_Statistics_Table (entity Systems.Monitoring.InstanceStatistics) and in cloud telemetry (Azure).
-
Collected & when: by the background telemetry service once per day (23:50 UTC) and on forced runs (e.g., server shutdown/start).
Daily Exec/Wait stats with automatic cleanup
Once per day, execution and wait statistics are captured and then cleared. This keeps reports fresh, highlights slow operations faster, and shortens troubleshooting time.
-
Where users see it:
-
Exec Stats: Navigator → Instance Statistics (read-only) and System.Monitoring.ExecStats.
-
Wait Stats: instance-level waits in Instance Statistics; server-level waits are cloud-only.
-
-
Stored in: local DB (Sys_Instance_Statistics_Table / Systems.Monitoring.InstanceStatistics) and cloud telemetry (Azure).
-
Collected & when: daily at 23:50 UTC and automatically on reset/shutdown/start; after capture, stats are cleared. Time windows reflect the period since the last reset
Every 5 minutes: performance counter snapshots
At calendar-aligned 5-minute intervals, the system collects CPU, memory, and other key counters for timely performance analysis.
-
Where users see it: not shown in the app UI (by design).
-
Stored in: cloud telemetry (Azure).
-
Collected & when: every calendar 5 minutes by the background telemetry service.
Availability & licensing (how local vs. cloud storage works)
-
Local statistics (DB): stored in Sys_Instance_Statistics_Table only when the Track Changes (X14) license is active.
-
Cloud telemetry (Azure): always collected for complete visibility, regardless of license.
-
This keeps databases lean without X14, while higher plans get advanced local views.
What you get
-
Transparent view of database growth and real server load.
-
Faster pinpointing of slow queries and lock waits.
-
More accurate capacity planning and incident prevention.
-
Comparable data over time—daily trends plus 5-minute snapshots for deep dives.
-
Data available in the cloud for all customers, and locally (when X14 is active) for in-app reporting and monitoring.
3. Faster Cleanup of Attribute Change History (Job J35666)
One of the most challenging maintenance tasks has been cleaning up the history of attribute changes. In large systems, this log can grow to billions of records, consuming huge amounts of storage and slowing down background processes.
We have optimized the dedicated cleanup job (J35666) so that old attribute change logs are now removed much faster and in far greater volumes. Instead of deleting data in very small chunks, the job now clears millions of records in a single run.
For customers, this means:
-
More free database space
-
Smoother system performance
-
Faster alignment with data retention policies
The result is a leaner, more responsive system, even in environments with very large datasets.
You can read more about Job J35666 here: https://docs.erp.net/tech/advanced/jobs/J35666.html
0 Comments