ODBC Server Reference Manual

Transact-SQL Language
HP NonStop ODBC Server Reference Manual—429151-002
4-46
NonStop ODBC Server Compared With SQL Server
insert into employee
(empnum, first_name, last_name, deptnum,
jobcode, salary)
values (2001, "Dana", "Hall", 1010, 3001, 40000)
commit transaction
NonStop ODBC Server Compared With SQL Server
When used through the NonStop ODBC Server, BEGIN TRANSACTION differs from
the SQL Server implementation in the following ways:
NonStop ODBC Server Compared With NonStop SQL/MP
The corresponding NonStop SQL/MP statement is BEGIN WORK.
The primary difference between NonStop ODBC Server transactions and NonStop
SQL/MP transactions is that, in programs used with the NonStop ODBC Server, you
can specify a transaction name. The transaction name is provided primarily for
compatibility with SQL Server and is not meaningful in NonStop SQL/MP (because
transactions cannot be nested in NonStop SQL/MP).
COMMIT TRANSACTION
Use COMMIT TRANSACTION to mark the ending point of a user-specified transaction.
All database changes since the preceding BEGIN TRANSACTION statement become
permanent.
The COMMIT TRANSACTION statement has the following syntax:
transaction-name
is the name associated with the transaction. The transaction-name is optional
on COMMIT TRANSACTION, and is ignored.
Feature In SQL Server
In Programs Used With the
NonStop ODBC Server
Are nested transactions allowed? Yes No
Are transaction savepoints
allowed?
Yes Yes, but they are ignored. If you
want to roll back a transaction, you
must roll back the entire transaction.
Are DDL operations on a table
allowed within a user-defined
transaction?
No Yes, if the table is audited.
See DDL Statements Allowed in
User-Defined Transactions on
page 4-3.
COMMIT TRAN[SACTION] [ transaction-name ]