TMF Operations and Recovery Guide (G06.24+)

HP NonStop TMF Operations and Recovery Guide—522417-002
C-1
C Managing SQL Objects
This appendix summarizes how to create and manage audited HP
NonStop SQL/MP and HP NonStop SQL/MX objects on a TMF system. It includes
these topics:
Audited Objects
SQL objects consist of audited components that must reside on TMF data volumes.
For this reason, TMF is required for all systems on which SQL/MP and SQL/MX
objects are defined and managed.
In SQL/MP, you can set the AUDIT file attribute to determine whether a table, index, or
view that you create is audited. In SQL/MX, however, all objects are always audited;
the AUDIT attribute does not apply.
TMF Guidelines for SQL Objects
By default, the SQL/MP and SQL/MX conversational interfaces (SQLCI and MXCI,
respectively) automatically initiate TMF transactions for individual statements.
A TMF transaction explicitly defined using language statements such as BEGIN WORK
and COMMIT WORK is referred to as a “user-defined” TMF transaction. You can use
user-defined TMF transactions to ensure that if several statements are not executed
successfully, they are then aborted. The following SQL commands together constitute
a user-defined TMF transaction:
>> BEGIN WORK;
>> SELECT .....;
>> INSERT .....;
>> DELETE .....;
>> COMMIT WORK or ROLLBACK WORK;
For statements issued in a user-defined TMF transaction, the SQL conversational
interface does not initiate a system-defined TMF transaction. For DDL commands,
however, you should allow the SQL conversational interface to initiate TMF
transactions.
Topic Page
Audited Objects C-1
Impact of SQL Operations on Online Dumps C-8