Database Connection Tips
Additional Options for Importing Hadoop Tables
SAS Visual Analytics offers self-service options for importing data from BigInsights, Cloudera, Cloudera
Impala, Pivotal HAWQ, Hortonworks, MapR, and Pivotal HD. Each of these databases requires
separate setup by your administrator.
A common connection
type for all of these databases is to connect to Hive or HiveServer2,
and then import tables.
If the Hadoop cluster is configured with the SAS Embedded Process, then you can perform parallel loading
to the SAS LASR Analytic Server. In this case, indicate one of the following in the
Import Data window:
-
In the SAS system options field, specify the SAS_HADOOP_CONFIG_PATH environment variable. This is not necessary if your administrator has already specified the values.
-
In the Configuration field, specify the path to a Hadoop configuration file.
Specifying more options
might be necessary for your site. For information about setting up
parallel loading from Hadoop, see “Where Do I Locate My Analytics
Cluster” in SAS Visual Analytics: Installation and Configuration Guide (Distributed SAS LASR).
Additional Options for Importing ODBC Tables
The Specify
connection options field provides you with an additional way to connect to an ODBC database instead
of using a data source name. For more information about possible options, see the LIBNAME Statement Specifics
for ODBC topic in SAS/ACCESS for Relational Databases: Reference.
Additional Options for Importing Oracle Tables
The value for the Path field
is related to the net service name in the tnsnames.ora file. The tnsnames.ora
file is generated during the Oracle client installation on the machine
for the SAS Web Application Server. The file is typically stored in
an Oracle installation directory such as
/opt/oracle/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora.
The net service name for the connection information is in this file.
See the following figure:
Additional Options for Importing PostgreSQL Tables
The Schema field is not case sensitive when you browse for tables, but it is case sensitive when the import is performed. As a result, if
you specify a schema in the wrong case, you can successfully browse for a table, and
then select it in the Choose Tables window. However,
the import fails. In this case, contact your database administrator
for assistance with the schema name.
Additional Options for Importing Teradata Tables
The Teradata
Management Server
field is used to determine whether the SAS LASR Analytic Server is co-located on the
same data appliance. If the SAS LASR Analytic Server and the Teradata database are on the same data appliance, then make sure that the Teradata Management Server
field includes the host name that the SAS LASR Analytic Server
uses.
SAS Visual Analytics and the Teradata database can be configured to transfer data
in parallel when they
are not co-located on the same data appliance. For information about setting up parallel
loading, see the Where Do I Locate My
Analytics Cluster topic in SAS Visual Analytics: Installation and Configuration Guide (Distributed SAS LASR).
Copyright © SAS Institute Inc. All Rights Reserved.