![]() |
VOOZH | about |
SAS is a software suite developed for advanced analytics, multivariate analysis, business intelligence, data management, and predictive analytics. When you pair SAS with the CData ODBC Driver for Phoenix, you gain database-like access to live Phoenix data from SAS, expanding your reporting and analytics capabilities. This article explains how to create a library for Phoenix in SAS and create a simple report based on real-time Phoenix data.
The CData ODBC Driver offers unmatched performance for interacting with live Phoenix data in SAS due to optimized data processing built into the driver. When you issue complex SQL queries from SAS to Phoenix, the driver pushes supported SQL operations, like filters and aggregations, directly to Phoenix and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can easily visualize and analyze Phoenix data in SAS.
Information for connecting to Phoenix follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Phoenix must be installed on the machine hosting the SAS System).
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.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
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.
If you are installing the CData ODBC Driver for Phoenix in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
[CData ApachePhoenix Sys] Driver = CData ODBC Driver for Phoenix Description = My Description Server = localhost Port = 8765
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Connect to Phoenix in SAS by adding a library based on the CData ODBC Driver for Phoenix.
SAS natively supports querying data either using a low-code, point-and-click Query tool or programmatically with PROC SQL and a custom SQL query. When you create a View in SAS, the defining query is executed each time the view is queried. This means that you always query live Phoenix data for reports, charts, and analytics.
proc sql; create view mytable_view as select id, column1 from odbclib.mytable where Id = '123456'; quit;
With a local view created, you can report, visualize, or otherwise analyze Phoenix data using the powerful SAS features. Print a simple report using PROC PRINT and create a basic graph based on the data using PROC GCHART.
proc print data=mytable; title "Phoenix MyTable Data"; run;π A simple Phoenix data report.
proc gchart data=mytable; pie id / sumvar=column1 value=arrow percent=arrow noheading percent=inside plabel=(height=12pt) slice=inside value=none name='MyTableChart'; run;π A simple Phoenix data chart.
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.