Problem Note 18988: Netezza support for remote external tables interface for SAS/ACCESS®
Interface to ODBC
More and more customers are accessing Netezza as a datasource in the
SAS/ACCESS Interface to ODBC engine, and in order to speed up writes
from SAS to Netezza, we need to implement the Netezza Remote External
Tables interface, which is Netezza's version of a bulk loader, RET
loader. Without this new interface, you will be unable to use the
RET loader as well as be unable to create tables with double columns or
update/delete any data except via PROC SQL Pass-Through.
To obtain this support, apply the hotfix.
NOTE: On Unix, you have to run with Netezza 3.1 or later to get the
loads to work properly due to an incompatibility between earlier
versions of Netezza and SAS/ACCESS to ODBC.
Once the HOTFIX is applied, to activate, all you have to do is add
BULKLOAD=YES to the data set. This way, it will use the default named
pipe interface to load data from SAS to Netezza. Other options that
customers can use with Netezza:
BL_USE_PIPE=YES|NO - defaults to YES; when NO, uses a flat file (that
can be specified with BL_DATAFILE)
BL_DATAFILE=<path and filename> - data file that SAS will use if
BL_USE_PIPE=NO; not valid for USE_PIPE=YES
BL_DELETE_DATAFILE=YES|NO - defaults to YES; when NO and USE_PIPE=NO,
SAS will not delete the flat file we create for
the load
BL_DELIMITER='<any single character>' - Defaults to '|'; this is the
delimiter that SAS uses between columns in the
data stream; customers should set this to a
character that doesn't appear in their data.
BL_OPTIONS='<set of Netezza-specific options>' - Any text entered here
will be added to the USING clause of the Netezza
CREATE EXTERNAL TABLE clause that is used for the
bulkload. This allows customers to specify any
of the external_table_options listed in the
Netezza
Database User's Guide.
Examples:
/* Using pipes */
data target.testbl(bulkload=yes);
set source.mytable;
run;
/* Using flat file (which won't be deleted at end) and specifying a */
/* different delimiter */
data target.testbl(bulkload=yes
bl_use_pipe=no
bl_delete_datafile=no
bl_datafile='c:\myfile.dat'
bl_delimiter=',');
set source.mytable;
run;\
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to ODBC | Microsoft Windows XP Professional | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows NT Workstation | 9.1 TS1M3 | |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.2 TS1M0 |
64-bit Enabled HP-UX | 9.1 TS1M3 | 9.2 TS1M0 |
Linux | 9.1 TS1M3 | 9.2 TS1M0 |
64-bit Enabled Solaris | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows 2000 Server | 9.1 TS1M3 | 9.2 TS1M0 |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | 9.2 TS1M0 |
64-bit Enabled AIX | 9.1 TS1M3 | 9.2 TS1M0 |
Tru64 UNIX | 9.1 TS1M3 | 9.2 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Topic: | SAS Reference ==> LIBNAME Engines Third Party ==> Information Exchange ==> ODBC (Open Database Connectivity)
|
Date Modified: | 2006-12-06 10:28:52 |
Date Created: | 2006-11-16 10:30:53 |