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

Data Set Options for Relational Databases 4 DBFORCE= Data Set Option 301Valid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, Informix, Microsoft SQL Server, Netezza, ODBC, OLE DB,Oracle, Sybase, Sybase IQ, TeradataSyntaxDBFORCE=YES | NOSyntax DescriptionYESspecifies that rows that contain data values that exceed the length of the DBMScolumn are inserted, and the data values are truncated to fit the DBMS columnlength.NOspecifies that the rows that contain data values that exceed the DBMS column lengthare not inserted.DetailsThis option determines how the SAS/ACCESS engine handles rows that contain datavalues that exceed the length of the DBMS column. DBFORCE= works only when youcreate a DBMS table with the DBTYPE= data set option—namely, you must specifyboth DBTYPE= and this option. DBFORCE= does not work for inserts or updates.Therefore, to insert or update a DBMS table, you cannot use the DBFORCE=option—you must instead specify the options that are available with SAS procedures.For example, specify the FORCE= data set option in SAS with PROC APPEND.FORCE= overrides DBFORCE= when you use FORCE= with PROC APPEND or thePROC SQL UPDATE statement. PROC SQL UPDATE does not warn you before ittruncates data.ExampleIn this example, two librefs are associated with Oracle databases, and it does notspecify databases and schemas because it uses the defaults. In the DATA step,MYDBLIB.DEPT is created from the Oracle data that MYORALIB.STAFF references.The LASTNAME variable is a character variable of length 20 in MYORALIB.STAFF.When MYDBLIB.DEPT is created, the LASTNAME variable is stored as a column oftype character and length 10 by using DBFORCE=YES.libname myoralib oracle user=tester1 password=tst1;libname mydblib oracle user=lee password=dataman;data mydblib.dept(dbtype=(lastname=’char(10)’)dbforce=yes);set myoralib.staff;run;