New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove custom TransactionManager #57

Closed
hisystems opened this Issue Apr 23, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@hisystems
Owner

hisystems commented Apr 23, 2012

A custom Transaction Manager was implemented in order to manage handling transaction start, commit and rollback in conjunction with the TransactionScope. To achieve this the OLEDBSERVICES=-3 option is specified (http://msdn.microsoft.com/en-us/library/windows/desktop/ms724518(v=vs.85).aspx) in the connection string which effectively disables managing of transactions so that the TransactionManager could manage the transactions. However, doing so limits the functionality of the TransactionScope construct with regard to distributed transactions. So, using distributed transactions should be re-enabled.

Unfortunately, this change will probably mean that the BEING/COMMIT/ROLLBACK TRANSACTIONs will not be logged via the StatementExecuted event.

@ghost ghost assigned hisystems Apr 23, 2012

@hisystems

This comment has been minimized.

Owner

hisystems commented May 5, 2012

Created issue Add support for LocalTransactionScope so that should distributed transactions not be required the LocalTransactionScope construct can instead be utilised which will implement just database transactions. This will therefore also include transaction logging statements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment