Re: [Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

You have basically only one option. 2PC. But that's not something ADO.NET handles. -- Mgr. Jiří Činčura Independent IT Specialist -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi

Re: [Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

Thanks for getting back to me. Can you or anyone please let me know what is the recommended approach in the ADO.NET provider for performing a transaction across, let's say, 2 databases (eg a single command in each)? On 5 November 2016 at 08:37, Jiří Činčura wrote: > I don't

Re: [Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

I don't think the TransactionScope block is a good idea here (well, it never is). Having it between multiple databases mean spinning MSDTC and enlisting there. I don't remember from top of my head whether that works in FirebirdClient or not. And the ChangeDatabase is ADO.NET non-sense for MS SQL.

[Firebird-net-provider] Subsequent error 'lock conflict on no wait transaction' using TransactionScope across DBs

Hi Jiri and all, We are running FB v2.5, and I am using the ADO v5.5.0 DLL to connect from my VS2013 C# project to 4 different databases. I have a little tool for user management, and to narrow the focus, one of the operations is to delete the user by: - REVOKE ALL GRANTs across all DBs - DROP