SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

792 Autopartitioning Scheme for Teradata 4 Chapter 28disconnect from tera2;quit;In this next example, MODE=TERADATA is specified to avoid case-insensitivebehavior. Because Teradata Mode is used, SQL COMMIT statements are not required./* Create & populate the table in Teradata mode (case insensitive). */proc sql;connect to teradata (user=testuser pass=testpass mode=teradata);execute(create table casetest(x char(28)) ) by teradata;execute(insert into casetest values(’Case Insensitivity Desired’) ) by teradata;quit;/* Query the table in Teradata mode (for case-insensitive match). */proc sql;connect to teradata (user=testuser pass=testpass mode=teradata);select * from connection to teradata (select * fromcasetest where x=’case insensitivity desired’);quit;Autopartitioning Scheme for TeradataOverviewFor general information about this feature, see “Autopartitioning Techniques in SAS/ACCESS” on page 57.The FastExport Utility is the fastest available way to read large Teradata tables.FastExport is NCR-provided software that delivers data over multiple Teradataconnections or sessions. If FastExport is available, SAS threaded reads use it. IfFastExport is not available, SAS threaded reads generate partitioning WHERE clauses.Using the DBSLICE= option overrides FastExport. So if you have FastExport availableand want to use it, do not use DBSLICE=. To use FastExport everywhere possible, useDBSLICEPARM=ALL.Note: FastExport is supported only on z/OS and UNIX. Whether automaticallygenerated or created by using DBSLICE=, partitioning WHERE clauses is notsupported. 4FastExport and Case SensitivityIn certain situations Teradata returns different row results to SAS when usingFastExport, compared to reading normally without FastExport. The difference arisesonly when all of these conditions are met:3 A WHERE clause is asserted that compares a character column with a characterliteral.3 The column definition is NOT CASESPECIFIC.Unless you specify otherwise, most Teradata native utilities create NOTCASESPECIFIC character columns. On the other hand, SAS/ACCESS Interface toTeradata creates CASESPECIFIC columns. In general, this means that you do notsee result differences with tables that SAS creates, but you might with tables thatTeradata utilities create, which are frequently many of your tables. To determine