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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>SAS</strong>/<strong>ACCESS</strong> Interface to DB2 Under z/OS 4 Column Selection <strong>for</strong> MOD Partitioning 491Autopartitioning Scheme <strong>for</strong> DB2 Under z/OSOverviewAutopartitioning <strong>for</strong> <strong>SAS</strong>/<strong>ACCESS</strong> Interface to DB2 under z/OS is a modulo (MOD)method. Threaded reads <strong>for</strong> DB2 under z/OS involve a trade-off. A threaded read witheven distribution of rows across the threads substantially reduces elapsed time <strong>for</strong> your<strong>SAS</strong> step. So your job completes in less time. This is positive <strong>for</strong> job turnaround time,particularly if your job needs to complete within a constrained period of time. However,threaded reads always increase the CPU time of your <strong>SAS</strong> job and the workload onDB2. If increasing CPU consumption or increasing DB2 workload <strong>for</strong> your job areunacceptable, you can turn threaded reads off by specifying DBSLICEPARM=NONE. Toturn off threaded reads <strong>for</strong> all <strong>SAS</strong> jobs, set DBSLICEPARM=NONE in the <strong>SAS</strong>restricted options table.For general in<strong>for</strong>mation about this feature, see “Autopartitioning Techniques in <strong>SAS</strong>/<strong>ACCESS</strong>” on page 57.Autopartitioning Restrictions<strong>SAS</strong>/<strong>ACCESS</strong> Interface to DB2 under z/OS places additional restrictions on thecolumns that you can use <strong>for</strong> the partitioning column during the autopartitioningphase. Here are the column types that you can partition.3 INTEGER3 SMALLINT3 DECIMAL3 You must confine eligible DECIMAL columns to an integer range—specifically,DECIMAL columns with precision that is less than 10. For example,DECIMAL(5,0) and DECIMAL(9,2) are eligible.Column Selection <strong>for</strong> MOD PartitioningIf multiple columns are eligible <strong>for</strong> partitioning, the engine queries the DB2 systemtables <strong>for</strong> in<strong>for</strong>mation about identity columns and simple indexes. Based on thein<strong>for</strong>mation about the identity columns, simple indexes, column types, and columnnullability, the partitioning column is selected in order by priority:1 Identity column2 Unique simple index: SHORT or INT, integral DECIMAL, and then nonintegralDECIMAL3 Nonunique simple index: SHORT or INT (NOT NULL), integral DECIMAL (NOTNULL), and then nonintegral DECIMAL (NOT NULL)4 Nonunique simple index: SHORT or INT (nullable), integral DECIMAL (nullable),and then nonintegral DECIMAL (nullable)5 SHORT or INT (NOT NULL), integral DECIMAL (NOT NULL), and thennonintegral DECIMAL (NOT NULL)6 SHORT or INT (nullable), integral DECIMAL (nullable), and then nonintegralDECIMAL (nullable)

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

Saved successfully!

Ooh no, something went wrong!