Reporting Database Replication

Workflow includes an option to install a reporting database. This database can be used with any valid reporting tool, and allows you to build ad-hoc reports on up-to-date data that you synchronize from your production database.

For more information on synchronizing your databases, see Reporting.

Note: If you plan on frequent synchronization for reporting purposes, we recommend that you replicate your database and run reporting against the replicated database. This measure reduces the risk of system timeout or shutdown due to locking of tables in the production database. If, upon trying to save data after replication, you receive an error similar to "System.Data.SqlClient.SqlException (0x80131904): Length of LOB data (88064) to be replicated exceeds configured maximum 65536," use SQL statements to increase the volume of data to replicate.

For information on setting up database replication, visit the Microsoft Developer Network website and review the article, SQL Server Replication.

When upgrading the application, if you are using a replicated database and have replication turned on, you must turn it off, upgrade, and then turn it on again. You must also upgrade the replicated database.

Synchronization SQL Statements


sp_configure 'max text repl size', 2147483647
GO
RECONFIGURE
GO

We recommend that you install the reporting database on a separate computer from the production database to prevent performance issues on the production database. Because the reporting database is installed on a separate computer, you must configure the connection between the production server and database, and the reporting server and database. You configure this connection when you install the reporting database. For more information, see Install the reporting database.

If, for any reason, you need to uninstall the reporting database, you are given the choice of completely removing the database from the computer or simply disconnecting the synchronization association between the databases. If you choose to disconnect synchronization, you can still run reports on the data that remains in the database.

The reporting database utilizes a reporting schema. To understand how to use the reporting database and generate your reports, you must understand the reporting schema defined for the Reporting Database. For more information, see Reporting Database Schema.

Important: We assume that Reporting Database users are experienced SQL users who are familiar with the SQL Server reporting tool or other reporting tools.

Note: Before you start using the Reporting Database, we recommend that you deploy the sample auditing reports that are included in the installation to view the data synchronization status.