Data Set Options for Relational Databases DBFORCE= Data Set Option 173
libname mydblib db2 user=testuser
pwd=testpass dsn=sample;
data mydblib.temp (DBCREATE_TABLE_OPTS=’PARTITIONING
KEY (X) USING HASHING’);
x=1; output;
x=2; output;
run;
Given this data set option, the following DB2 SQL statement is passed by the
SAS/ACCESS interface to DB2 in order to create the DB2 table:
CREATE TABLE TEMP (X DOUBLE) PARTITIONING
KEY (X) USING HASHING
See Also
To assign this option to a group of relational DBMS tables or views, see the
LIBNAME option “DBCREATE_TABLE_OPTS= LIBNAME Option” on page 87.
DBFORCE= Data Set Option
Specifies whether to force the truncation of data during insert processing
Valid in:
DATA and PROC steps (when accessing DBMS data using SAS/ACCESS
software)
DBMS support: DB2 OS/390, DB2 UNIX/PC, Informix, ODBC, OLE DB, Oracle, Microsoft
SQL Server, SYBASE, Teradata
Default value:
NO
Syntax
DBFORCE=YES | NO
Syntax Description
YES
specifies that the rows which contain data values that exceed the length of the
DBMS column are inserted, and the data values are truncated to fit the DBMS
column length.
NO
specifies that the rows which contain data values that exceed the DBMS column
length are not inserted.
Details
This option determines how the SAS/ACCESS engine handles rows that contain data
values that exceed the length of the DBMS column.
