Using a replicated database with ReportManager
To offload the processing burden of report generation from the live SiriusSQL server, some clients replicate their database and use the replicated database for reporting purposes only.
To facilitate these configurations, ReportManager works with dual connections – one to a live database and one to a replicated database. To use dual connections, check the check box on the SysManager > Preferences > Miscellaneous > Manager tab named Force Dual Connections for Report Manager. ReportManager looks for this setting when it starts. If this setting is checked, ReportManager does not start unless the replicated database and ODBC connector is specified in the [Data] section of the ReportManager.INI file. This is very, very important for those clients who replicate for reporting purposes. If a client connects using an instance of ReportManager that is not set up for dual connections, it breaks replication.
You must set the .INI settings on each ReportManager station. You need to add a new ODBC connector that points to the replicated database. You need ODBC connectors for both your live database and the replicated database, as shown below:
Example:
[Data]
ODBC_DSN=SiriusSQL
Database=SiriusSQL
Replication_ODBC_DSN=SiriusSQL_Replicated
Replication_Database=SiriusSQL_Seminar_R