Setting &SPDSEV2T=2 forces SPD Server to use parallel reads when
returning data even if the data is sorted.  This option does not mask
the sort order from the SAS client.  This can lead to situations where
the sort order is expected by the client application, but records are
not returned in sorted order.  Errors and incorrect results can be
produced. SQL Joins and GROUP BY clauses have been identified as a
possible processes affected by this.

Note that as documented in the SPD Server documentation, "this problem
does not apply to SQL statements executed via the SPD Server
pass-through SQL mechansim".


As a result, we recommend not using &SPDSEV2T=2.  If you have sorted
data and want to have the SPD Server return data in sorted order, use
the dataset option SORTEDBY=_NULL_.  This will hide the sort order from
both the client procedure and SPD Server, freeing it up to use parallel
reads.


SPDSEV1T controls whether parallel reads are used when reading indexed
data.  Using &SPDSEV1T=2 is discouraged for similar reasons.  Instead,
we recommend using &SPDSNIDX=YES to have the server block index usage.

Operating System and Release Information