Hi,
In some
scenarios in my Silverlight application, I need to use transactions on server
side. I noticed that the transaction is promoted to Distributed Transaction
when querying or saving (almost with a unique EntitityManager).
I
understand that for scalability reasons and multi-server environments this is
necessary.
Is there
any options to set to avoid this to happen ?
Unfortunately
Windows Azure platform doesn’t support distributed transactions !
Regards