2d. Install a database system to handle the ETL_Temp database | Questionmark

2d. Install a database system to handle the ETL_Temp database

Applies to the following products: 
Questionmark Perception
Applies to the following Perception versions: 
Perception 5.7

Your ETL server needs to have the following prerequisites installed (apart from a database system):

You can install .NET 4.0 manually or automatically, using the appropriate Web Platform Installer link below. IIS must be installed manually.

A database system for the ETL_Temp database needs to be installed on your ETL server.

A database is needed on the same server where the ETL service is installed to hold result data while it is being readied for the Results Warehouse. Because your Extract, Transform, and Load service is on a different server from the database, it becomes more efficient to ETL the data to a local database and then move it to the destination database in the correct format. This is illustrated in the diagram below:

For instructions on how to install either SQL Server, please refer to the accompanying documentation of each database system. Once you have installed the database system you will be using for the ETL service, see the appropriate section below to configure your database system for use with Perception.

SQL Server

Make sure that the SQL Server authentication mode is set to Mixed Mode (SQL Server authentication and Windows authentication).

Enable TCP/IP

The following network options that are disabled by default will need to be enabled.

  1. Open SQL Server Configuration Manager.
  2. Expand SQL Server Network Configuration, and select Protocols.
  3. Enable TCP/IP and Named Pipes.
  4. Close the SQL Server Configuration Manager.

Start SQL Browser

  1. Open SQL Server Configuration Manager.
  2. Click SQL Server Services in the left-hand pane, or double-click SQL Server Services in the right-hand pane.
  3. Start SQL Server Browser.

Add Firewall exceptions

If you have a software firewall installed on your server, you will need to add exceptions for incoming and outgoing database communication on TCP/IP ports.

After you have configured this, continue to step 2e using the link below.