Determines the length of very large DBMS character data types, such as BLOB or CLOB, that are read into SAS or written from SAS when you are using a SAS/ACCESS engine.
| Valid in: | DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software) |
|---|---|
| Alias: | TEXTSIZE= |
| Default: | 1024 |
| Restrictions: | This option applies when you retrieve, append, and update rows in an existing table. It does not apply when you create a table. |
| This option is ignored for CHAR, VARCHAR, and VARCHAR2 (Oracle) data types. | |
| Requirements: | Specify this value as 4000 when you are using procedures that work with SAS High-Performance Analytics Server. [Oracle] |
| Specify this value as 4000 or lower when you are using procedures that work with the SAS High-Performance Analytics Server. [Amazon Redshift, DB2, Hadoop, Impala, JDBC, Microsoft SQL Server, ODBC, PostgreSQL, SAP HANA, Spark] | |
| Data source: | Amazon Redshift, Aster, DB2 under UNIX and PC Hosts, Greenplum, Hadoop, HAWQ, Impala, JDBC, MySQL, Microsoft SQL Server, Netezza, ODBC, OLE DB, Oracle, PostgreSQL, SAP ASE, SAP HANA, SAP IQ, Snowflake, Spark, Vertica, Yellowbrick |
| Note: | Support for Spark and Yellowbrick was added in SAS 9.4M7. |
| See: | DBMAX_TEXT= LIBNAME option |
Table of Contents
In general, this option applies only to BLOB, CLOB, and other large object or very long DBMS character data types, such as the SAP ASE TEXT data type. Also, remember that the number of bytes that are used to store characters might vary and is based on your session encoding.
If the way that you specify the value of DBMAX_TEXT= truncates data in a table, the data load fails for that table.
Hadoop: This option applies for the STRING data type.
Oracle: For SAS 9 or higher, this option applies for CLOB, BLOB, LONG, LONG RAW, and LOB data types. The behavior of the ACCESS and DBLOAD procedures has not changed since SAS 8. So only LONG and LOB data types are valid if you use this option with those procedures.