Separate SQL statements, whether contained within a transaction or not, are
sent to the job queue separately, and thus processed by whatever server
process happens to become idle next. This is the only way to go: if a
transaction means 'insert new money to one account - delete old money from
another - commit both' then there could be dirty great pauses at each point
where I've put a hyphen. Pauses would tie up a server process, and prevent
it from working for others. In other words, you -with your lackadaisical
approach to typing- would have effectively grabbed a dedicated server
process for your own ends. Rather defeats the purpose of MTS, doesn't it?!
Regards
HJR
"Y" <y_at_y.y> wrote in message news:3CF445C5.12EA1578_at_y.y...
> I am using Oracle 8i EE.
>
> In MTS, shared server processes switch between working for the requests
> from the user processes. These server processes work in a round-robin
> fashion.
>
> Someone would tell me WHEN a server process could switch and is ready to
> service the next request??? Is it when the server process finishes the
> whole transaction OR when the server process finishes the whole sql
> statement?
>
> TIA
>
Received on Wed May 29 2002 - 00:29:27 CDT
