SlicingDice Documentation

SlicingDice - The All-in-One Solution Documentation

Welcome to the SlicingDice documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Configuring Workbench/J

SlicingDice does not provide or install any SQL client tools or libraries.

If you already have a business intelligence application or any other application that can connect to your SlicingDice using a standard JDBC or ODBC driver, you can use them. If you still don't have an application that can connect to your database, this section presents one option for doing so using SQL Workbench/J, a free, DBMS-independent, cross-platform SQL query tool.

SlicingDice's JDBC driver with Workbench/J video guide

Watch this quick video below to learn how to use SlicingDice's JDBC driver with Workbench/J.

Download and install SlicingDice Drivers and Workbench/J

In order to use the JDBC driver, we kindly ask you to download and install SlicingDice JDBC SQL Driver and the Workbench/J.

  1. Download and install the SlicingDice's JDBC driver:

  2. Download and install the SQL Workbench/J tool:


SQL Workbench/J requires the Java Runtime Environment (JRE) be installed on your system. Ensure you are using the correct version of the JRE required by the SQL Workbench/J client. To determine which version of the Java Runtime Environment is running on your system, do one of the following:

  • Mac: In the System Preferences, click the Java icon.
  • Windows: In the Control Panel, click the Java icon.
  • Any system: In a command shell, type java -version.

For information about installing and configuring the Java Runtime Environment, go to

SlicingDice driver configuration on Workbench/J

  1. Open SQL Workbench/J.

  2. Click File, and then click Connect window.

  3. Click Create a new connection profile.

  4. In the New profile box, type a name for the profile. For example, examplecluster_jdbc.

  5. Click Manage Drivers. The Manage Drivers dialog opens. In the Name box, type a name for the driver.

  1. Click the folder icon next to the Library box, navigate to the location of the driver, click it, and then click Open.

Find the folder where the SlicingDice driver was installed, select cdata.jdbc.slicingdice.jar and click OK. SQL Workbench/J automatically completes the Classname box. Leave the Sample URL box blank, and then click OK.

  1. In the Driver box, select the driver you just added.

  2. For the URL field, copy the JDBC URL below and paste it there.


As you can see, this line above contains the space for you to insert your Database Key (or a Custom Database Key).

For more information about finding the Database Key to complement the URL, see how to create a database page.

  1. Leave the Username and Password fields blank/empty. SlicingDice only requires the Database Key to connect to a database.

  2. Select the Autocommit box.

  3. Click the Save profile list icon, as shown below:

  1. Click OK. Workbench/J is now configured with SlicingDice JDBC driver.

Test the SQL Workbench/J connection

After you configure your JDBC or ODBC connection, you can test the connection by typing and running an example query into the Statement window.

SELECT * FROM default;

In this case, default represents the default dimension of your database, that is automatically added once you create a new database on SlicingDice.

If your connection is successful and your database is empty, this result will show on the Results tab.

Alternatively, if you already have some data stored on the database, running the SQL query above would bring the list of all your columns and its data. Example:

Success! Now you are all set to move forward and insert and query data on your SlicingDice database using SQL and Workbench/J.

If you are having any issues to connect to your database or if your query returned a different result, please, contact us through the online chat.

Configuring Workbench/J

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.