![]() |
VOOZH | about |
The CData ODBC Driver for Phoenix enables you to link to Phoenix data in Microsoft Power Query, ensuring that you see any updates. This article details how to use the ODBC driver to import Phoenix data into Microsoft Power Query.
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Connect to Apache Phoenix via the Phoenix Query Server. Set the Server and Port (if different from the default port) properties to connect to Apache Phoenix. The Server property will typically be the host name or IP address of the server hosting Apache Phoenix.
By default, no authentication will be used (plain). If authentication is configured for your server, set AuthScheme to NEGOTIATE and set the User and Password properties (if necessary) to authenticate through Kerberos.
Follow the steps below to import Phoenix data using standard SQL:
From the ribbon in Excel, click Power Query -> From Other Data Sources -> From ODBC.
Provider=MSDASQL.1;Persist Security Info=False;DSN=CData ApachePhoenix Source
Enter the SELECT statement to import data with. For example:
SELECT Id, Column1 FROM MyTable WHERE Id = '123456'👁 The ODBC connection string and SELECT query. (Salesforce is shown.)
Enter credentials, if required, and click Connect. The results of the query are displayed in the Query Editor Preview. You can combine queries from other data sources or refine the data with Power Query formulas. To load the query to the worksheet, click the Close and Load button.
👁 Tables loaded in Power Query. (Salesforce is shown.)Download a free trial of the Phoenix ODBC Driver to get started:
Download NowLearn more:
👁 Apache Phoenix IconThe Phoenix ODBC Driver is a powerful tool that allows you to connect with HBase through Apache Phoenix, directly from any applications that support ODBC connectivity.
Access Phoenix like you would a relational database - read, write, and update through a standard ODBC Driver interface.