Creating reports on data is an important part of any business and Workflow provides a reporting database for you to install that is specially designed to facilitate reporting and analysis. You can use any valid reporting tool with the reporting database and you have the flexibility to design your own ad-hoc reports.
After you install the reporting database, you can synchronize it with your production database so that you can run reports on up-to-date data.
You use the
Reporting Schedule Editor to synchronize your databases. You can synchronize your databases based on a scheduled event, or you can synchronize manually. For example, if you need to run a report a week before the databases are scheduled to synchronize, you can use the
Synchronize Now button on the
Reporting Schedule Editor. Be aware, however, that the
Synchronize Now button is not available if there are unsaved changes to the
Reporting Schedule Editor.
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
Workflow