To enable report users from production environment to run reports on secondary SQL servers with near real-time data from production, one way to do it is to restore the database on the secondary report server as read-only so the data can be synced continuously from production. Two SQL server configurations are presented here to sync data from a production DXE database server to the secondary server with a read-only database.
For information, refer to the Microsoft documentation at following links:
|
Figure 1. Setup for read-only report servers in an Always-on Availability Group. In this group, a minimum of two databases is required: a primary replica as the production database and a synchronous secondary replica with a read-only database. You can use this read-only replica as a report server. You can also add additional synchronous or asynchronous replicas to provide more redundancy and capability. A report server can be set up either on a synchronous replica or on an asynchronous replica. A "DentrixRW" database is required for each replica. |
For information, refer to the Microsoft documentation at the following link:
|
Figure 2. Using log shipping to create read-only secondary report servers. More than one secondary server can be set up and configured to run multiple report servers. All of the secondary databases are updated with log shipping. Some of the DXOne Reporting reports can be configured to run against the secondary database on a read-only report server. A "DentrixRW" database is required for each database server. |
