13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Data Set Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 PARTITION_KEY= Data Set Option 357SyntaxORHINTS=’Oracle-hint’Syntax DescriptionOracle-hintspecifies an Oracle hint <strong>for</strong> <strong>SAS</strong>/<strong>ACCESS</strong> to pass to the DBMS as part of an SQLquery.DetailsIf you specify an Oracle hint, <strong>SAS</strong> passes the hint to Oracle. If you omit ORHINTS=,<strong>SAS</strong> does not send any hints to Oracle.ExamplesThis example runs a <strong>SAS</strong> procedure on DBMS data and <strong>SAS</strong> converts the procedureto one or more SQL queries. ORHINTS= enables you to specify an Oracle hint <strong>for</strong> <strong>SAS</strong>to pass as part of the SQL query.libname mydblib oracle user=testuser password=testpass path=’myorapath’;proc print data=mydblib.payroll(orhints=’/*+ ALL_ROWS */’);run;In the next example, <strong>SAS</strong> sends the Oracle hint ’/*+ ALL_ROWS */’ to Oracle aspart of this statement:SELECT /*+ ALL_ROWS */ * FROM PAYROLLPARTITION_KEY= Data Set OptionSpecifies the column name to use as the partition key <strong>for</strong> creating fact tables.Default value: noneValid in: DATA and PROC steps (when accessing DBMS data using <strong>SAS</strong>/<strong>ACCESS</strong>software)DBMS support: Aster nClusterSyntaxPARTITION_KEY=’column-name’DetailsYou must enclose the column name in quotation marks.Aster nCluster uses dimension and fact tables. To create a data set in Aster nClusterwithout error, you must set both the DIMENSION= and PARTITION_KEY=(LIBNAME or data set) options.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!