The SQL Workshop
section configures various aspects of the SQL Workshop.
SQL Commands Maximum Inactivity in minutes: This
sets the maximum time in minutes that a transaction can be inactive
before it times out and issues a rollback. This is to prevent a
locking problem to persist if a transaction is not committed in the
SQL Workshop.
SQL Scripts Maximum Script Output Size in bytes:
This sets the maximum amount of bytes of output that a script can
produce. The output from a script will not be rendered until it has
completed. If there is a run-away script or plain SELECT statement
producing a large amount of data, it may cause the page to take a
long time to be rendered. This setting will limit the amount of
information.
SQL Scripts Maximum Workspace Output Size in
Bytes: This setting limits that amount of output that any
particular workspace can produce. This setting is designed to
prevent network problems that may be caused by a workspace that is
inefficient and placing a burden on the other workspaces.
SQL Scripts Maximum Script size in bytes: This
setting limits the script size which can be submitted through the
SQL Workshop. The Administrator may want to limit this to prevent
the user from consuming too much buffer space. Each SQL Script will
consume buffer space in memory.
Enable Transactional SQL Commands: Setting this
value will allow users to submit many commands in a single database
transaction: otherwise, the user must submit the commands
singularly.
