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

162 OR_ENABLE_INTERRUPT= LIBNAME Option 4 Chapter 10YESattempts to send as many inserts to Teradata that can fit in a 64K buffer. Ifmultistatement inserts are not possible, processing reverts to single-row inserts.NOsend inserts to Teradata one row at a time.DetailsWhen you request multistatement inserts, SAS first determines how many insertstatements that it can send to Teradata. Several factors determine the actual numberof statements that SAS can send, such as how many SQL insert statements can fit in a64K buffer, how many data rows can fit in the 64K data buffer, and how many insertsthe Teradata server chooses to accept. When you need to insert large volumes of data,you can significantly improve performance by using MULTISTMT= instead of insertingonly single-row.When you also specify the DBCOMMIT= option, SAS uses the smaller of theDBCOMMIT= value and the number of insert statements that can fit in a buffer as thenumber of insert statements to send together at one time.You cannot currently use MULTISTMT= with the ERRLIMIT= option.See AlsoTo apply this option to an individual data set or a view descriptor, see the“MULTISTMT= Data Set Option” on page 348.OR_ENABLE_INTERRUPT= LIBNAME OptionAllows interruption of any long-running SQL processes on the DBMS server.Default value: NOValid in: SAS/ACCESS LIBNAME statementDBMS support: OracleSyntaxOR_ENABLE_INTERRUPT=YES | NOSyntax DescriptionYESenables interrupt of long-running SQL processes on the DBMS server.NOdisables interrupt of long-running SQL processes on the DBMS server.DetailsYou can use this option to interrupt these statements: