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

70 In-Database Procedure Considerations and Limitations 4 Chapter 83 The LIBNAME statement must point to a valid version of the DBMSs:3 Teradata server running version 12 or above for Linux3 DB2 UDB9.5 Fixpack 3 running only on AIX or Linus x643 Oracle 9i.In-Database Procedure Considerations and LimitationsOverviewThe considerations and limitations in the following sections apply to both Base SASand SAS/STAT in-database procedures.Note: Each in-database procedure has its own specific considerations andlimitations. For more information, see the documentation for the procedure. 4Row Order3 DBMS tables have no inherent order for the rows. Therefore, the BY statementwith the NOTSORTED option, the OBS option, and the FIRSTOBS option willprevent in-database processing.3 The order of rows written to a database table from a SAS procedure is not likely tobe preserved. For example, the SORT procedure can output a SAS data set thatcontains ordered observations. If the results are written to a database table, theorder of rows within that table might not be preserved because the DBMS has noobligation to maintain row order.3 You can print a table using the SQL procedure with an ORDER BY clause to getconsistent row order or you can use the SORT procedure to create an ordinary SASdata set and use the PRINT procedure on that SAS data set.BY-GroupsBY-group processing is handled by SAS for Base SAS procedures. Raw results arereturned from the DBMS, and SAS BY-group processing applies formats as necessary tocreate the BY group.For SAS/STAT procedures, formats can be applied, and BY-group processing can occurinside the DBMS if the SAS_PUT( ) function and formats are published to the DBMS.For more information, see the SAS Analytics Accelerator for Teradata: User’s Guide.The following BY statement option settings apply to the in-database procedures:3 The DESCENDING option is supported.3 The NOTSORTED option is not supported because the results are dependent onrow order. DBMS tables have no inherent order for the rows.By default, when SAS/ACCESS creates a database table, SAS/ACCESS uses the SASformats that are assigned to variables to decide which DBMS data types to assign tothe DBMS columns. If you specify the DBFMTIGNORE system option for numericformats, SAS/ACCESS creates DBMS columns with a DOUBLE PRECISION data type.For more information, see the “Overview of the LIBNAME Statement for Relational