ElasticSearch Connector for SSASRead / write ElasticSearch data inside your app; perform many ElasticSearch operations without coding, just use easy to use high performance API Connector for ElasticSearch In this article you will learn how to quickly and efficiently integrate ElasticSearch data in SSAS without coding. We will use high-performance ElasticSearch Connector to easily connect to ElasticSearch and then access the data inside SSAS. Let's follow the steps below to see how we can accomplish that! ElasticSearch Connector for SSAS is based on ZappySys API Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few. |
Connect to ElasticSearch in other apps
|
Create Data Source in ZappySys Data Gateway based on API Driver
-
Download and install ODBC PowerPack.
-
Search for gateway in start menu and Open ZappySys Data Gateway:
-
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:
-
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 API Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.
ElasticsearchDSN
-
When the Configuration window appears give your data source a name if you haven't done that already, then select "ElasticSearch" from the list of Popular Connectors. If "ElasticSearch" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
ElasticsearchDSNElasticSearch -
Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.
Steps how to get and use ElasticSearch credentials
For Local / Hosted Instance by you
- Get your userid / password and enter on the connection UI
For Managed Instance (By Bonsai search)
If your instance is hosted by bonsai then perform these steps to get your credentials for API call- Go to https://app.bonsai.io/clusters/{your-instance-id}/tokens
- Copy Access Key and Access Secret and enter on the connection UI. Click Test connection.
- If your Cluster has no data you can generate sample data by visiting this URL and click Add Sample Data https://{your-cluster-id}.apps.bonsaisearch.net/app/home#/tutorial_directory
Fill in all required parameters and set optional parameters if needed:
ElasticsearchDSNElasticSearchBasic Authentication (UserId/Password) [Http]http://localhost:9200Optional Parameters User Name (or Access Key) Password (or Access Secret) Ignore certificate related errors Fill in all required parameters and set optional parameters if needed:
ElasticsearchDSNElasticSearchWindows Authentication (No Password) [Http]http://localhost:9200Optional Parameters Ignore certificate related errors -
Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:
ZappySys API Driver - ElasticSearchRead / write ElasticSearch data inside your app; perform many ElasticSearch operations without coding, just use easy to use high performance API Connector for ElasticSearchElasticsearchDSN -
Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in SSAS to retrieve data from ElasticSearch. Hit OK button to use this query in the next step.
SELECT * FROM Indexes
Some parameters configured in this window will be passed to the ElasticSearch API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful datamuch faster . -
Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in SSAS:
ZappySys API Driver - ElasticSearchRead / write ElasticSearch data inside your app; perform many ElasticSearch operations without coding, just use easy to use high performance API Connector for ElasticSearchElasticsearchDSNSELECT * FROM Indexes
You can also access data quickly from the tables dropdown by selecting <Select table>.AWHERE
clause,LIMIT
keyword will be performed on the client side, meaning that thewhole result set will be retrieved from the ElasticSearch API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in ElasticSearch servers). -
Click OK to finish creating the data source.
Read ElasticSearch data in SSAS cube
With the data source created in the Data Gateway (previous step), we're now ready to read ElasticSearch data in an SSAS cube. Before we dive in, open Visual Studio and create a new Analysis Services project. Then, you're all set!
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!
-
Create a new data source:
-
Once a window opens,
select Create a data source based on an existing or new connection option and
click New...:
-
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.
ElasticsearchDSNElasticsearchDSNIf 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
-
Indeed, life is easy again:
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!
-
Start by right-clicking on Data Source Views and then choosing New Data Source View...:
-
Select the previously created data source and click Next:
- Ignore the Name Matching window and click Next.
-
Add the tables you will use in your SSAS cube:
For cube dimensions, consider creating a Virtual Table in the Data Gateway's data source. Use the
DISTINCT
keyword in theSELECT
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 ElasticSearch. -
Review your data source view and click Finish:
-
Add the missing table relationships and you're done!
Create cube
We have a data source view ready to be used by our cube. Let's create one!
-
Start by right-clicking on Cubes and selecting New Cube... menu item:
-
Select tables you will use for the measures:
-
And then select the measures themselves:
-
Don't stop and select the dimensions too:
-
Move along and click Finish before the final steps:
-
Review your cube before processing it:
-
It's time for the grand finale! Hit Process... to create the cube:
-
A splendid success!
Execute MDX query
The cube is created and processed. It's time to reap what we sow! Just execute an MDX query and get ElasticSearch data in your SSAS cube:

Actions supported by ElasticSearch Connector
Learn how to perform common ElasticSearch actions directly in SSAS with these how-to guides:
- Count documents
- Create Index
- Delete documents
- Delete Index
- Get document by ID from Index or Alias
- Get documents from Index or Alias
- Get Index or Alias metadata
- Insert documents
- List aliases
- List indexes
- Search / Query documents
- Update documents
- Upsert documents
- Generic Request
- Generic Request (Bulk Write)
Conclusion
In this article we showed you how to connect to ElasticSearch in SSAS and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys API Driver allows you to connect not only to ElasticSearch, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).
We encourage you to download ElasticSearch 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 ElasticSearch Connector for SSAS Documentation
More integrations
Other connectors for SSAS
Other application integration scenarios for ElasticSearch
How to connect ElasticSearch in SSAS?
How to get ElasticSearch data in SSAS?
How to read ElasticSearch data in SSAS?
How to load ElasticSearch data in SSAS?
How to import ElasticSearch data in SSAS?
How to pull ElasticSearch data in SSAS?
How to push data to ElasticSearch in SSAS?
How to write data to ElasticSearch in SSAS?
How to POST data to ElasticSearch in SSAS?
Call ElasticSearch API in SSAS
Consume ElasticSearch API in SSAS
ElasticSearch SSAS Automate
ElasticSearch SSAS Integration
Integration ElasticSearch in SSAS
Consume real-time ElasticSearch data in SSAS
Consume real-time ElasticSearch API data in SSAS
ElasticSearch ODBC Driver | ODBC Driver for ElasticSearch | ODBC ElasticSearch Driver | SSIS ElasticSearch Source | SSIS ElasticSearch Destination
Connect ElasticSearch in SSAS
Load ElasticSearch in SSAS
Load ElasticSearch data in SSAS
Read ElasticSearch data in SSAS
ElasticSearch API Call in SSAS