# Splitting GUI and Database for Sonata Reports

**URL:** <https://forums.vitalpbx.org/t/splitting-gui-and-database-for-sonata-reports/5825>\
**Category:** VitalPBX\
**Created:** [November 4, 2025, 9:37am UTC](https://forums.vitalpbx.org/t/splitting-gui-and-database-for-sonata-reports/5825 "2025-11-04T09:37:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Edson.junior](https://forums.vitalpbx.org/user_avatar/forums.vitalpbx.org/edson.junior/32/4281_2.png) [@Edson.junior](https://forums.vitalpbx.org/u/Edson.junior)\
**Post date:** [November 4, 2025, 9:37am UTC](https://forums.vitalpbx.org/t/splitting-gui-and-database-for-sonata-reports/5825/1 "2025-11-04T09:37:54Z")

</div>

Hi everyone,

I’m exploring a setup for the Sonata Reports module and would like to know if the following architecture is feasible:

- **Machine 1:** hosts the GUI (graphical interface) for Sonata Reports
- **Machine 2:** runs a dedicated database for the reports

The goal is to offload processing from the main server and avoid performance issues by separating the reporting workload.

Has anyone implemented something similar? Is it possible to have the GUI on Machine 1 querying a separate database on Machine 2 without compromising performance or data integrity?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![system](https://forums.vitalpbx.org/uploads/default/original/1X/672b458a1d454755270c2c16adc5316b641c3c6a.png) [@system](https://forums.vitalpbx.org/u/system)\
**Post date:** [December 4, 2025, 9:38am UTC](https://forums.vitalpbx.org/t/splitting-gui-and-database-for-sonata-reports/5825/2 "2025-12-04T09:38:28Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.