Apache Derby Connector for SSAS

Apache Derby Connector enables you to connect to Apache Derby, a lightweight, open-source relational database management system (RDBMS).

In this article you will learn how to quickly and efficiently integrate Apache Derby data in SSAS without coding. We will use high-performance Apache Derby Connector to easily connect to Apache Derby and then access the data inside SSAS.

Let's follow the steps below to see how we can accomplish that!

Download Documentation

Prerequisites

Before we begin, make sure you meet the following prerequisite:

If you already have a JRE installed, you can try using it too. However, if you experience any issues, we recommend using one of the distributions mentioned above (you can install an additional JRE next to the existing one; just don't forget to configure the default Java in the Windows Environment Variables).

Download Apache Derby JDBC driver

To connect to Apache Derby in SSAS, you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

  1. Visit Apache Derby website.
  2. Follow the instructions there, download the JDBC drivers, and save them locally.
    It is recommended to use JDBC driver compiled for Java 8, if possible.
  3. Done! That was easy, wasn't it? Let's proceed to the next step.

Create Data Source in ZappySys Data Gateway based on JDBC Bridge Driver

  1. Download and install ODBC PowerPack.

  2. Search for gateway in start menu and Open ZappySys Data Gateway:

    Open ZappySys Data Gateway
  3. Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:

    ZappySys Data Gateway - Add User
  4. Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys JDBC Bridge Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.

    ApacheDerbyDSN
    Native - ZappySys JDBC Bridge Driver
    ZappySys Data Gateway - ZappySys JDBC Bridge Driver
  5. Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

    ApacheDerbyDSN
    jdbc:derby://hostname:1527/mydatabase
    org.apache.derby.jdbc.ClientDriver
    D:\Apache\derby\lib\derbyclient.jar
    admin
    **************
    []
    JDBC-ODBC Bridge driver data source settings

    For Client/server Environment, use these values when setting parameters:

    • Connection string: jdbc:derby://hostname:1527/mydatabase
    • Driver class: org.apache.derby.jdbc.ClientDriver
    • JDBC driver file(s): D:\Apache\derby\lib\derbyclient.jar
    • User name: admin
    • User password: **************
    • Connection parameters: []

    For Embedded Environment, use these values when setting parameters:

    • Connection string: jdbc:derby:c:\apache\derby\databases\mydatabase
    • Driver class: org.apache.derby.jdbc.EmbeddedDriver
    • JDBC driver file(s): D:\Apache\derby\lib\derby.jar

  6. You should see a message saying that connection test is successful:

    ODBC connection test is successful

    Otherwise, if you are getting an error, check out our Community for troubleshooting tips.

  7. We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:

    ApacheDerbyDSN
    SELECT * FROM "APP"."ORDERS"
    JDBC ODBC Bridge data source preview
    SELECT * FROM "APP"."ORDERS"
    You can also click on the <Select Table> dropdown and select a table from the list.

    The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the Trino JDBC driver, which then handles the query execution. This means the Bridge Driver simply relays the SQL query without altering it.

    Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.

  8. Click OK to finish creating the data source.

Read Apache Derby data in SSAS cube

With the data source created in the Data Gateway (previous step), we're now ready to read Apache Derby data in an SSAS cube. Before we dive in, open Visual Studio and create a new Analysis Services project. Then, you're all set!

In the example below, we use Multidimensional and Data Mining Analysis Services project, but it should work with Tabular project too.

Create data source based on ZappySys Data Gateway

Let's start by creating a data source for a cube, based on the Data Gateway's data source we created earlier. So, what are we waiting for? Let's do it!

  1. Create a new data source: Create new data source in SSAS to read API data
  2. Once a window opens, select Create a data source based on an existing or new connection option and click New...: Connect to ZappySys Data Gateway in SSAS to read API data
  3. Here things become a little complicated, but do not despair, it's only for a little while. Just perform these little steps:
    • Select Native OLE DB\SQL Server Native Client 11.0 as provider.
    • Enter your Server name (or IP address) and Port, separated by a comma.
    • Select SQL Server Authentication option for authentication.
    • Input User name which has admin permissions in the ZappySys Data Gateway.
    • In Database name field enter the same data source name you use in the ZappySys Data Gateway.
    • Hopefully, our hard work is done, when we Test Connection.
    ApacheDerbyDSN
    ApacheDerbyDSN
    Configure new data source in SSAS to read API data
    If SQL Server Native Client 11.0 is not listed as Native OLE DB provider, try using these:
    • Microsoft OLE DB Driver for SQL Server
    • Microsoft OLE DB Provider for SQL Server
  4. Indeed, life is easy again: Test connection to ZappySys Data Gateway in SSAS to read API data

Add data source view

We have data source in place, it's now time to add a data source view. Let's not waste a single second and get on to it!

  1. Start by right-clicking on Data Source Views and then choosing New Data Source View...: Create new data source view in SSAS to read API data
  2. Select the previously created data source and click Next: Connect to ZappySys Data Gateway in SSAS to read API data
  3. Ignore the Name Matching window and click Next.
  4. Add the tables you will use in your SSAS cube: Select tables to read API data in SSAS cube
    For cube dimensions, consider creating a Virtual Table in the Data Gateway's data source. Use the DISTINCT keyword in the SELECT statement to get unique values from the facts table, like this:
    SELECT DISTINCT Country FROM Customers
    For demonstration purposes we are using sample tables which may not be available in Apache Derby.
  5. Review your data source view and click Finish: Successful data source view creation in SSAS
  6. Add the missing table relationships and you're done! Create additional table relationships in SSAS to read API data

Create cube

We have a data source view ready to be used by our cube. Let's create one!

  1. Start by right-clicking on Cubes and selecting New Cube... menu item: Create new SSAS cube to read API data
  2. Select tables you will use for the measures: Choose measure tables in SSAS to read API data
  3. And then select the measures themselves: Selecting measures for SSAS cube to read API data
  4. Don't stop and select the dimensions too: Choosing dimensions for SSAS cube to read API data
  5. Move along and click Finish before the final steps: Read API data in SSAS cube
  6. Review your cube before processing it: Read API data in SSAS cube
  7. It's time for the grand finale! Hit Process... to create the cube: Process SSAS cube to read API data
  8. A splendid success! SSAS cube processed to read API data

Execute MDX query

The cube is created and processed. It's time to reap what we sow! Just execute an MDX query and get Apache Derby data in your SSAS cube:

Execute MDX in SSAS cube to read API data

Conclusion

In this article we showed you how to connect to Apache Derby in SSAS and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys JDBC Bridge Driver allows you to connect not only to Apache Derby, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Apache Derby Connector for SSAS and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Apache Derby Connector for SSAS Documentation

More integrations

Other connectors for SSAS

All
Big Data & NoSQL
Database
CRM & ERP
Marketing
Collaboration
Cloud Storage
Reporting
Commerce
API & Files

Other application integration scenarios for Apache Derby

All
Data Integration
Database
BI & Reporting
Productivity
Programming Languages
Automation & Scripting
ODBC applications

  • How to connect Apache Derby in SSAS?

  • How to get Apache Derby data in SSAS?

  • How to read Apache Derby data in SSAS?

  • How to load Apache Derby data in SSAS?

  • How to import Apache Derby data in SSAS?

  • How to pull Apache Derby data in SSAS?

  • How to push data to Apache Derby in SSAS?

  • How to write data to Apache Derby in SSAS?

  • How to POST data to Apache Derby in SSAS?

  • Call Apache Derby API in SSAS

  • Consume Apache Derby API in SSAS

  • Apache Derby SSAS Automate

  • Apache Derby SSAS Integration

  • Integration Apache Derby in SSAS

  • Consume real-time Apache Derby data in SSAS

  • Consume real-time Apache Derby API data in SSAS

  • Apache Derby ODBC Driver | ODBC Driver for Apache Derby | ODBC Apache Derby Driver | SSIS Apache Derby Source | SSIS Apache Derby Destination

  • Connect Apache Derby in SSAS

  • Load Apache Derby in SSAS

  • Load Apache Derby data in SSAS

  • Read Apache Derby data in SSAS

  • Apache Derby API Call in SSAS