Ready to get started?

Learn more about the CData JDBC Driver for SQL Analysis Services or download a free trial:

Download Now

Create a Data Access Object for SQL Analysis Services Data using JDBI

A brief overview of creating a SQL Object API for SQL Analysis Services data in JDBI.

JDBI is a SQL convenience library for Java that exposes two different style APIs, a fluent style and a SQL object style. The CData JDBC Driver for SQL Analysis Services integrates connectivity to live SQL Analysis Services data in Java applications. By pairing these technologies, you gain simple, programmatic access to SQL Analysis Services data. This article walks through building a basic Data Access Object (DAO) and the accompanying code to read and write SQL Analysis Services data.

Create a DAO for the SQL Analysis Services Adventure_Works Entity

The interface below declares the desired behavior for the SQL object to create a single method for each SQL statement to be implemented.

public interface MyAdventure_WorksDAO { //insert new data into SQL Analysis Services @SqlUpdate("INSERT INTO Adventure_Works (Fiscal_Year, Sales_Amount) values (:fiscal_Year, :sales_Amount)") void insert(@Bind("fiscal_Year") String fiscal_Year, @Bind("sales_Amount") String sales_Amount); //request specific data from SQL Analysis Services (String type is used for simplicity) @SqlQuery("SELECT Sales_Amount FROM Adventure_Works WHERE Fiscal_Year = :fiscal_Year") String findSales_AmountByFiscal_Year(@Bind("fiscal_Year") String fiscal_Year); /* * close with no args is used to close the connection */ void close(); }

Open a Connection to SQL Analysis Services

Collect the necessary connection properties and construct the appropriate JDBC URL for connecting to SQL Analysis Services.

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.

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the SQL Analysis Services JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.ssas.jar

Fill in the connection properties and copy the connection string to the clipboard.

A connection string for SQL Analysis Services will typically look like the following:

jdbc:ssas:User=myuseraccount;Password=mypassword;URL=http://localhost/OLAP/msmdpump.dll;

Use the configured JDBC URL to obtain an instance of the DAO interface. The particular method shown below will open a handle bound to the instance, so the instance needs to be closed explicitly to release the handle and the bound JDBC connection.

DBI dbi = new DBI("jdbc:ssas:User=myuseraccount;Password=mypassword;URL=http://localhost/OLAP/msmdpump.dll;"); MyAdventure_WorksDAO dao = dbi.open(MyAdventure_WorksDAO.class); //do stuff with the DAO dao.close();

Read SQL Analysis Services Data

With the connection open to SQL Analysis Services, simply call the previously defined method to retrieve data from the Adventure_Works entity in SQL Analysis Services.

//disply the result of our 'find' method String sales_Amount = dao.findSales_AmountByFiscal_Year("FY 2008"); System.out.println(sales_Amount);

Write SQL Analysis Services Data

It is also simple to write data to SQL Analysis Services, using the previously defined method.

//add a new entry to the Adventure_Works entity dao.insert(newFiscal_Year, newSales_Amount);

Since the JDBI library is able to work with JDBC connections, you can easily produce a SQL Object API for SQL Analysis Services by integrating with the CData JDBC Driver for SQL Analysis Services. Download a free trial and work with live SQL Analysis Services data in custom Java applications today.