Access SQL Analysis Services Data as a Remote Oracle Database

The Oracle Database Gateway for ODBC and Heterogeneous Services technology enable you to connect to ODBC data sources as remote Oracle databases. This article shows how to use the CData ODBC Driver for SQL Analysis Services to create a database link from SQL Analysis Services to Oracle and to query SQL Analysis Services data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to SQL Analysis Services as an ODBC Data Source

Information for connecting to SQL Analysis Services follows, along with different instructions for configuring a DSN in Windows and Linux environments.

To connect, provide authentication and set the Url property to a valid SQL Server Analysis Services endpoint. You can connect to SQL Server Analysis Services instances hosted over HTTP with XMLA access. See the Microsoft documentation to configure HTTP access to SQL Server Analysis Services.

To secure connections and authenticate, set the corresponding connection properties, below. The data provider supports the major authentication schemes, including HTTP and Windows, as well as SSL/TLS.

• HTTP Authentication

  Set AuthScheme to "Basic" or "Digest" and set User and Password. Specify other authentication values in CustomHeaders.

• Windows (NTLM)

  Set the Windows User and Password and set AuthScheme to "NTLM".

• Kerberos and Kerberos Delegation

  To authenticate with Kerberos, set AuthScheme to NEGOTIATE. To use Kerberos delegation, set AuthScheme to KERBEROSDELEGATION. If needed, provide the User, Password, and KerberosSPN. By default, the data provider attempts to communicate with the SPN at the specified Url.

• SSL/TLS:

  By default, the data provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats.

You can then access any cube as a relational table: When you connect the data provider retrieves SSAS metadata and dynamically updates the table schemas. Instead of retrieving metadata every connection, you can set the CacheLocation property to automatically cache to a simple file-based store.

See the Getting Started section of the CData documentation, under Retrieving Analysis Services Data, to execute SQL-92 queries to the cubes.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Note: If you need to modify the DSN or create other SQL Analysis Services DSNs, you must use a system DSN and the bitness of the DSN must match your Oracle system. You can access and create 32-bit DSNs on a 64-bit system by opening the 32-bit ODBC Data Source Administrator from C:\Windows\SysWOW64\odbcad32.exe.

Linux

If you are installing the CData ODBC Driver for SQL Analysis Services in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Set Connection Properties for Compatibility with Oracle

The driver provides several connection properties that streamline accessing SQL Analysis Services data just as you would an Oracle database. Set the following properties when working with SQL Analysis Services data in SQL*Plus and SQL Developer. For compatibility with Oracle, you will need to set the following connection properties, in addition to authentication and other required connection properties.

• MapToWVarchar=False

  Set this property to map string data types to SQL_VARCHAR instead of SQL_WVARCHAR. By default, the driver uses SQL_WVARCHAR to accommodate various international character sets. You can use this property to avoid the ORA-28528 Heterogeneous Services data type conversion error when the Unicode type is returned.

• MaximumColumnSize=4000

  Set this property to restrict the maximum column size to 4000 characters.

• IncludeDualTable=True

  Set this property to mock the Oracle DUAL table. SQL Developer uses this table to test the connection.

Linux Configuration

In Linux environments, Oracle uses UTF-8 to communicate with the unixODBC Driver manager, whereas the default driver encoding is UTF-16. To resolve this, open the file /opt/cdata/cdata-driver-for-ssas/lib/cdata.odbc.ssas.ini in a text editor and set the encoding.

cdata.odbc.ssas.ini

Configure the ODBC Gateway, Oracle Net, and Oracle Database

Follow the procedure below to set up an ODBC gateway to SQL Analysis Services data that enables you to query live SQL Analysis Services data as an Oracle database.

1. Create the file initmyssasdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:

   initmyssasdb.ora

   HS_FDS_CONNECT_INFO = "CData SSAS Sys"
2. Add an entry to the listener.ora file. This file is located in oracle-home-directory/NETWORK/admin.

   If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myssasdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = dg4odbc) ) )

   If you are using Heterogeneous Services, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = myssasdb) (ORACLE_HOME = your-oracle-home) (PROGRAM = hsodbc) ) )

3. Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:

   tnsnames.ora

   myssasdb = (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)) (CONNECT_DATA=(SID=myssasdb)) (HS=OK) )
4. Restart the listener.

5. Test the configuration with the following command:

   tnsping myssasdb

6. Open SQL*Plus and create the database link with the command below:

   CREATE DATABASE LINK myssasdb CONNECT TO "user" IDENTIFIED BY "password" USING 'myssasdb';

You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):