![]() |
VOOZH | about |
ETL Validator provides data movement and transformation capabilities for integrating data platforms across your organization. CData's JDBC driver seamlessly integrates with ETL Validator and extends its native connectivity to include SQL Analysis Services data.
This tutorial explains how to build a simple ETL validator data flow to extract data from SQL Analysis Services data and load it into an example data storage solution: SQL Server.
CData extends ETL Validator's data connectivity capabilities by providing the ability to add data sources that connect via CData's JDBC drivers. Connecting to SQL Analysis Services data simply requires creating a new data source in ETL Validator through CData's connectiviy suite as described below.
Begin by logging into ETL Validator to view the application dashboard.
π Access the ETL Validator dashboardCData extends the data source options within ETL Validator.
π Create a new DataSourceCData's connectivity is embedded within ETL Validator's data source options.
π CData data sourceYou will need a JDBC connection string to establish a connection to SQL Analysis Services in ETL Validator.
π CData data sourceTo 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.
Set AuthScheme to "Basic" or "Digest" and set User and Password. Specify other authentication values in CustomHeaders.
Set the Windows User and Password and set AuthScheme to "NTLM".
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.
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.
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
A typical connection string looks like this:
jdbc:ssas:User=myuseraccount;Password=mypassword;URL=http://localhost/OLAP/msmdpump.dll;
To ensure the JDBC driver is licensed appropriately, copy the license file to the appropriate location:
Copy the JDBC Driver for SQL Analysis Services and lic file from "C:\Program Files\CData[product_name]\lib" to "C:\Datagaps\ETLValidator\Server\apache-tomcat\bin".
cdata.jdbc.ssas.jar cdata.jdbc.ssas.lic
Note: If you do not copy the .lic file with the jar, you will see a licensing error that indicates you do not have a valid license installed. This is true for both the trial and full versions.
Should you encounter any difficulties loading the CData JDBC driver class, please contact DataGap's team, and they will provide you instructions on how to load the jar file for the relevant driver.
This example will use SQL Server as a destination for SQL Analysis Services data data, but any preferred destination can be used instead.
This option is the default.
π Add SQL ServerThe details will depend on the specific target, but these details may include a URL, authentiation credentials, etc.
π Add SQL ServerConfigured data flows will appear in this window.
π Dataflows tabName your new dataflow and save it.
The details of the data movement will be configured in this panel.
π Dataflow diagramGive the new source an appropriate name and save it.
π Jira example sourceSelect the Table from the Schema option that reflects which data should be pulled from SQL Analysis Services data.
The anticipated outcome of the configured query is displayed in the Result tab.
π Query resultsSelect Switch to Diagram, then drag & drop the DB Sink as a target from the right side (under Sink options). Give the sink an appropriate name and save it.
π Data sinkChoose the Schema and table that matches the structure of the source table. For this example, the table on the target side was created to match the Source so that data flow seamlessly. More advanced schema transformation operations are beyond the scope of this article.
π Destination schemaRunning the job will take some time.
π Destination schemaReturn to the diagram to see the finished data replication job from SQL Analysis Services data to SQL Server.
π Full dataflowDownload a free, 30-day trial of the CData JDBC Driver for SQL Analysis Services and start building SQL Analysis Services-connected applications with ETL Validator. Reach out to our Support Team if you have any questions.
Download a free trial of the SQL Analysis Services Driver to get started:
Download NowLearn more:
π SQL Server Analysis Services IconRapidly create and deploy powerful Java applications that integrate with SQL Analysis Services.