Rick,

> Is a new transaction started after a commit command in an isql script?

No, according to the output of a trace session. A transaction gets
automatically started once you execute a new statement.

So each statement in an isql script is a new transaction? Is there any

> way to force the whole script to be one transaction?
>

Unless you're using autocommit, a transaction starts when you execute any
statement and continues until you explicitly commit it or roll it back.
What Thomas was saying is that a commit doesn't immediately start a new
transaction. Instead, isql waits until it sees a statement that needs a
transaction (e.g. select, insert, create, update, delete, etc.) and starts
the transaction before running the statement. Subsequent statements run in
the same transaction until you explicitly end the transaction.

Good luck,

Ann


[Non-text portions of this message have been removed]