Install the reporting database

The reporting database allows you to use the data synchronized from your production database to build reports for your facility. You can use any reporting tool to extract the information from the reporting database and create your reports.

Before you begin

You must have installed a supported SQL Serve version before you install the reporting database (see Software Requirements). In addition, you must select the SQL Server Integration Service (SSIS) component when you install SQL Server. Select the SQL Reporting Services component, as well, if you want to use SQL as your reporting tool.
Note: We recommend that you install the reporting database on a separate computer from the production database to prevent performance issues on the production database. In this scenario, additional configuration changes are required. Refer to Configure Component Services for more information. However, if the application server computer meets the requirements for both databases, they can be installed on the same computer.

About this task

If more than one version of SQL Server is installed, the integration services used for the reporting database will be the most recent version.
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.
Example:
sp_configure 'max text repl size', 2147483647
GO
RECONFIGURE
GO

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

Procedure

  1. From the application splash screen, click Install Reporting Database.
    Note: If this splash screen does not appear, run SetupReporting.exe on the root directory of the installation folders.
    The License Agreement page appears.
  2. Review the license agreement, and then click I Agree.
    The Installation Folder page appears.
  3. Accept the default destination folder or browse for a new location, and then click Next.
  4. In the Configure Reporting SQL Server area, enter the following information, and then click Next.
    1. In the Server field, accept the default value if the reporting database is on the local machine with the default instance. If the SQL Server named instance is used, enter the SQL Server name and instance name; for example, <servername>\<instance name>.
      Note: The reporting SQL Server must be local.
    2. In the Database field, enter the name of the reporting database. This creates a new database; however, if a database of the same name already exists, this database will append to the existing one.
    3. From the Authentication list, select the type of authentication you want to use. If you choose to use integrated security, select Windows Authentication; otherwise, select SQL Server Authentication, and then enter the user name and password for the SQL Server.
  5. In the Configure SQL Server area, perform one of the following actions:
    • Leave the Use a local SQL database with Windows Authentication check box selected, and then click Next.
    • Clear the Use a local SQL database with Windows Authentication check box, enter the following information, and then click Next.

      1. In the SQL field, enter the name of the SQL Server where the SQL database is located.
      2. In the Database field, enter the name of the production (SQL) database that you will connect to for synchronization.
      3. From the Authentication list, select the type of authentication you want to use. If you choose to use integrated security, select Windows Authentication; otherwise, select SQL Server Authentication, and then enter the user name and password for the SQL Server.
  6. In the Workflow Server Configuration area, enter the following information, and then click Next.
    • In the Server computer name field, enter the fully qualified name of the server computer.
  7. In the Configure Security area, enter an administrator user name and password.
    Important:
    • You cannot use a Windows user name and password to configure security for the reporting database; it must be a valid Windows administrator user name and password.
    • The Advanced user authentication settings (Use SSO, Allow Password Change, Enforce User Lockout, and Enforce Password Complex Rules) do not apply when installing the reporting database.
  8. Click Install.
  9. When the installation is complete, click Exit.