Last modified: January 09, 2012
Applies to: Windows | Windows Server
The JetBeginTransaction2 function causes a session to enter a transaction and create a new save point. This function can be called more than once in a single session to create additional save points. These save points can be used to selectively to keep or discard changes to the database.
JET_ERR JET_API JetBeginTransaction2( __in JET_SESID sesid, __in JET_GRBIT grbit );
The session to use for this call.
A group of bits that contain the options to be used for this call, which include zero or more of the following.
The transaction will not modify the database. If an update is attempted, that operation will fail with JET_errTransReadOnly. This option is ignored unless it is requested when the given session is not already in a transaction. This option is only available as of Windows XP.
This function returns the JET_ERR datatype with one of the following return codes. For more information about the possible ESE errors, see Extensible Storage Engine Errors and Error Handling Parameters.
The operation completed successfully.
It is not possible to complete the operation because all activity on the instance associated with the session has ceased as a result of a call to JetStopService.
It is not possible to complete the operation because the instance associated with the session has encountered a fatal error that requires that access to all data be revoked to protect the integrity of that data.
This error will only be returned by Windows XP and later releases.
It is not possible to complete the operation because the instance associated with the session has not been initialized yet.
It is not possible to complete the operation because a restore operation is in progress on the instance associated with the session.
The same session cannot be used for more than one thread at the same time. This error will only be returned by Windows XP and later releases.
It is not possible to complete the operation because the instance associated with the session is being shut down.
A new transaction cannot be started because the session is already at the maximum save point depth allowable by the database engine.
On success, the provided session will be inside a transaction. If the session was previously inside of a transaction then a new save point will be created.
On failure, the transactional state of the session will remain unchanged. No change to the database state will occur.
For more information about how transactions work, see JetBeginTransaction.
Requires Windows Vista, Windows XP, or Windows 2000 Professional.
Requires Windows Server 2008, Windows Server 2003, or Windows 2000 Server.
Declared in Esent.h.