Working with connections in Intelligence Reporting

Working with connections in Intelligence Reporting

Creating New Database Connection

A Data Connection holds the relevant connection information to connect to a supported ODBC or OLEDB compliant data source. This data connection object is then used for all connections to this data source. By adding a data connection the Connector can make data available from this data source.

To add a new data connection, double-click on the Enterprise object and select the relevant connection type (driver) to use for the connection, by clicking on it in the object window. Right select and select Add Connection.

tip1

In the Connection Name field, type the name of your connection.

tip2

NOTE: Depending on the connection type of the connection being created, certain values will need to be entered to specify how the data is accessed (some connection types will allow you to browse for data using the buttons to the right of the text boxes). Where paths or folder names are required for creating a Data Connection always use the Universal Naming Convention as opposed to using drive mappings. For example \Servernamecmydata as opposed to X:mydata where X is a mapped drive to \Servernamec. This will ensure that reports against this Data Connection can be run from any workstation regardless of drive mappings.

  1. In the Server box, browse to or add your server name
  2. In the Database Name box, enter the name of your Database
  3. In the User Id: text field, type your User Id: if you have security settings on the data folder
  4. In the Password text field, type your password for the above entered User Id
  5. Click on Add. The new Connection will now appear in the Object window

Testing Database Connections

  1. To test the Connection, right select on the Connection, select the Check/Test

tip3

Changing Database Connections

  1. Highlight the connection
  2. Edit the Properties in the properties window
  3. Select Apply

    • Related Articles

    • Sharing Report Shortcuts using Intelligence Reporting

      Problem When you create a report shortcut, it creates and points to a file within the AppData directory of the user that created the shortcut, which in turn points to the BICore.exe on the machine. When another user tries to run the report shortcut, ...
    • Downloading and Installing Intelligence Reporting

      1. Download Intelligence Reporting To download your version of Sage Intelligence, visit our website and choose the appropriate version. a) Visit our website here: https://www.alchemex.com.au/intelligence-reporting/#alchemextrial b) Choose the ...
    • Does Intelligence Reporting and CData support TLS 1.2?

      Question A recent upgrade from Microsoft has marked End of Life for TLS 1.0 and 1.1. I am using Intelligence Reporting and/or Cdata drivers selled by Alchemex and need to upgrade my servers. How will it affect my Reporting? Support for Intelligence ...
    • Testing Connections and Troubleshooting Connection Errors

      OVERVIEW One of the main functions of the Sage Intelligence software is to connect to a data source(s) and retrieve data; these connections are made through the appropriate ODBC driver(s). Because of this reliance on the ODBC drivers, errors can ...
    • Understanding Intelligence Reporting on Terminal Servers

      Intelligence Reporting licensing can be tricky, especially given the different license types and the possible network configurations. In this tip we’re going to look at the case of Citrix and or Terminal Server environments and consider the different ...