>there are a few optimizer options (eg, parallel_query, parallel_degree, scan_parallel_degree) that >can be set at the session, procedure and/or query level to enable/disable the ability to use parallel >worker threads
but will that restrict the usage of parallelism to only those transactions within the procedure/query level?
currently we have a shell script which sets parallelism options and within a loop executes reorg/create index. so looping is not within Sybase and so the parallel resources can be used by other transactions.
but if I code this in TSQL, can parallelism be restricted within the transaction (by using some special clause)?
appreciate the feedback.