ADF BC Support Distributed Transactions?

Hi ,
As my subject! I have two DataBase in my Fusion Application , ADF BC Support Distributed Transactions? How TO do this ?
Can you give me any advice ? thanks!!
Edited by: Shaowei.Zhang on 2010-9-2 下午8:23

Hi,
I see a bug filed to get documentation and clarification about this. I don't think ADF Business Components itself can do this using the JDBC URL connection. If then I imagine this to be doable using JDBC data sources. However, I am surely not the experts in this.
Frank
Ps.: The documentation bug has been filed recently and is in an internal review state

Similar Messages

Is HS Generic Connectivity(db2/400 odbc) supports Distributed Transaction?

hi,
Is HS Generic Connectivity(db2/400 odbc) supports Distributed Transaction?
I am getting an error as follows
"ORA-02047 cannot join the distributed transaction in progress" when i am trying a transaction, which is inserting in to db2/400 and updating in Oracle.
if it does not support this, what is the best way
to do such things using generic connectivity.
(eg. by committing each sql statement ?)
my db is oracle 9i 9.2.0.4.0
remote db is db2/400 connected with client access ODBC.
Thanks
BA

Hi,
one of the restrictions of generic connectivity is, that distributed transactions are not allowed.
See manual: 7-6 Oracle9 i Heterogeneous Connectivity Administrator's Guide
- Generic Connectivity agents cannot participate in distributed transactions; they
support single-site transactions only
So you can only commit after each statement or you have to use the GATEWAY

ADF- Jdev11.1.1.6 Business Components supports distributed transaction ?

Hi ,
I'm using Jdeveloper 11.1.1.6 release 1 . How to implement distributed transaction in ADF business component level.
In my scenario i need to perform A Single transaction with two different database . I do need to role back both if either one fails (Distributed Transactions) . How could i achieve this in ADF business component. Does ADF has any built-in support for Distributed transactions.
Could anybody advice me .
Thanks in Advanced .

Thanks for your response !!! What is the best alternative i can choose to achieve Distributed Transaction in ADF Application , if there is no inbuilt support for it in BC?
Edited by: 994058 on Mar 15, 2013 7:16 AM
Edited by: 994058 on Mar 15, 2013 7:18 AM

Distributed transactions and 2-phase commit in a SAP Netweaver environment

Hello,
I am a Java architect., I don't know very much the SAP technologies. I tried to found on forums or technical papers if SAP does support distributed transactions and two-phase commit, it's not clear. I found something on SAP WAS but my project is using a SAP PI 7.0 and I cannot find anything on the subject.
My goal is to include a SAP server (via PI 7.0) in a distributed transaction handled by a J2EE ESB (Oracle, ex-BEA Aqualogic) based on XA capabilities.
Does anyone have experience or feedback on this topic ?
Thanks.

Hi,
Do you know this white paper ?
[Distributed Transaction and 2 phase commit|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3732d690-0201-0010-a993-b92aab79701f]
Regards,
Olivier

ORA-02074: cannot ROLLBACK in a distributed transaction

I have a stored procedure that successfully creates a portal user when I run it with SQLPLUS.
However when I call the same procedure through ODP.Net, I get the following error.
"ORA-20001: ORA-02074: cannot ROLLBACK in a distributed transaction\nORA-06512: at \"PORTAL30.WWSEC_API\", line 1915\nORA-02074: cannot SET SAVEPOINT in a distributed transaction\nORA-06512: at \"PORTAL30.PRO_CREATE_WEB_USER\", line 28\nORA-06512: at line 1"
The portal version is 3.0.9.8.2 The stored proc is in the portal30 schema and I am connecting as portal30 user.
Any help is greatly appreciated...
Thanks.
The following is the code for the stored procedure:-
CREATE OR REPLACE PROCEDURE PORTAL30.PRO_CREATE_WEB_USER (
puser IN varchar2,
puser_last_name IN varchar2,
puser_first_name IN varchar2,
puser_group IN varchar2,
password IN varchar2
) AS
l_group_id number;
l_id number;
e_code number;
begin
l_id := wwsec_api.add_portal_user(p_User_Name => puser,p_Last_Name => puser_last_name,p_First_Name => puser_first_name,p_Portal_User => 'Y');
wwsec_api.activate_portal_user(puser);
portal30_sso.WWSSO_API_USER_ADMIN.CREATE_USER(P_USERNAME=> puser,P_PASSWORD=>password,p_error_code=> e_code);
wwsec_api.add_user_to_list(p_person_id => l_id,p_to_group_id => wwsec_api.group_id (p_name => puser_group),p_is_owner => wwsec_api.NOT_OWNER);
wwsec_api.set_defaultgroup(p_groupid => wwsec_api.group_id (p_name => puser_group),p_username => puser);
commit;
exception
when others then
raise_application_error(-20001,substr(sqlerrm,1,200));
end;
The foll is the code I am using to call the stored proc.
private void createUser()
string retval ;
OracleConnection oraconn = new OracleConnection(Data Source=testdb;User ID=portal30;Password=portal30" );
OracleCommand cmd = new OracleCommand("PRO_CREATE_WEB_USER", oraconn);
cmd.CommandType = CommandType.StoredProcedure;
OracleParameter a_uid = new OracleParameter("puser" ,OracleDbType.Varchar2,20);
a_uid.Direction = ParameterDirection.Input ;
a_uid.Value = (txtUserId.Text).Trim() ;
cmd.Parameters.Add(a_uid);
OracleParameter a_last_name = new OracleParameter("puser_last_name" ,OracleDbType.Varchar2,20);
a_last_name.Direction = ParameterDirection.Input ;
if (( txtLName.Text).Trim() != "" )
a_last_name.Value = (txtLName.Text).Trim() ;
else
a_last_name.Value = " ";
cmd.Parameters.Add(a_last_name);
OracleParameter a_first_name = new OracleParameter("puser_first_name" ,OracleDbType.Varchar2,20);
a_first_name.Direction = ParameterDirection.Input ;
if ((txtFName.Text).Trim() != "")
a_first_name.Value = (txtFName.Text).Trim() ;
else
a_first_name.Value = " ";
cmd.Parameters.Add(a_first_name);
OracleParameter a_type = new OracleParameter("puser_group" ,OracleDbType.Varchar2,20);
a_type.Direction = ParameterDirection.Input ;
a_type.Value = (lstUserType.SelectedValue).Trim() ;
cmd.Parameters.Add(a_type);
OracleParameter a_passwd = new OracleParameter("password" ,OracleDbType.Varchar2,20);
a_passwd.Direction = ParameterDirection.Input ;
a_passwd.Value = (txtPassword.Text).Trim() ;
cmd.Parameters.Add(a_passwd);
try
oraconn.Open();
cmd.ExecuteNonQuery();
lblMsg.ForeColor = System.Drawing.Color.FromName("blue");
lblMsg.Text = "User Created.";
catch(OracleException e)
{ retval = e.Message ;
lblMsg.ForeColor = System.Drawing.Color.FromName("red");
lblMsg.Text = "Error Creating user" ;
finally
oraconn.Close();

Also note that remote procedure/function calls (e.g. from ODP.NET), do not support distributed transactions (i.e. a SAVEPOINT/ROLLBACK block within the PL/SQL procedure/function) before database version Oracle 9i.
So if you are using say Oracle 817 you must use the "OracleTransaction" object in ODP.NET instead.
See:
http://www.dotnet247.com/247reference/msgs/39/197274.aspx

Distributed transactions/jdbc problem WL60

Hi
          Our company has aworking application running on WLS5.1sp9.
          Im in the process of migrating it to WL6.0sp2.
          Our domain has 2 clusters each running 2 servers:
          1) servlet engines (handling http requests from clients, running servlets
          and jsp's)
          2) ejb containers (runnigour entities and session beans, working with Oracle
          8i database using connection pool and TxDataSource)
          The scenario:
          - a client request invokes a servlet on one of the servlet engines.
          - the servlet opens a jndi context to one of the ejb containers
          - the servlet open a transaction on a UserTransaction stub on that ejb.
          - then the servlet calls an entity bean using a home interface looked up
          using the same context.
          - the entity bean uses DataSource lookup in its own servers jndi to rerieve
          a connection.
          and then i get the following exception:
          java.sql.SQLException: No default driver for database type:
          jdbc:weblogic:jts
          at
          weblogic.jdbcbase.t3.Driver.seeIfWeNeedToInferDriverNameAndUrlFrom(Driver.ja
          va:456)
          at weblogic.jdbcbase.t3.Driver.getAllPropsFrom(Driver.java:255)
          at weblogic.jdbcbase.t3.Driver.connect(Driver.java:75)
          at weblogic.jdbcbase.jts.Driver.createRemoteConnection(Driver.java:199)
          at weblogic.jdbcbase.jts.Driver.connect(Driver.java:134)
          at
          weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
          :44)
          at com.unisfair.util.DBHelper.getConnection(DBHelper.java:43)
          the transaction toString() gives:
          transaction=(IdHash=7541556,Name = [EJB
          UserBeanImpl.generateSessionSuffix()],Xid=2:b53da78d3c1badbb,Status=Active,n
          umRepliesOwedMe=0,numRepliesOwedOthers=1,seconds since begin=0,seconds
          left=30,activeThread=Thread[ExecuteThread: '8' for queue: 'default',5,Thread
          Group for Queue:
          'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assig
          ned=none),SCInfo[ejb2]=(state=active),SCInfo[servlet2]=(state=active),SCInfo
          [ejb1]=(state=active),properties=({weblogic.transaction.name=[EJB
          UserBeanImpl.generateSessionSuffix()], weblogic.jdbc=t3://10.0.0.31:7007}))
          However the error happens on the other ejb server 10.0.0.33:7007
          It seems that the jts driver tries to get a remote connection on the server
          that coordinates the transaction but uses the deprecated t3 driver.
          I hope someone can help us since this problem is a good enough reason for us
          not moving on to WL6.0 we also looked at WL6.1 Beta and theres nothing new
          about it either.
          thanks
          Dror Last
          Senior Software Engineer
          Unisfair Inc.
          12 Yad Haruzim St. Tel Aviv 67778 Israel
          Tel: +972-3-5373738 Ext. 243
          Fax: +972-3-5373731
          GSM: +972-55-723710
          mailto:[email protected]
          http://www.unisfair.com/


<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC_TX ():
In the readme file of Oracle JDBC drivers 8.1.6.0.1 (http://technet.oracle.com/software/tech/java/sqlj_jdbc/files/Readme_01.txt)
it mentioned that it supports "distributed transactions".
As I understand, JDBC transaction is connection based and uses Oracle internal transaction manager. In order to do "distributed transactions", I must have at least two connections open at the same time each to its own database instance. How does the two connections coordinate the transactions? I thought in order to support "distributed transactions", one has to build a higher layer to encapsulate the two connections and therefore coordinate the distributed transactions. Any examples will be welcome.<HR></BLOCKQUOTE>
The two branches of the transaction are coordinated using 2-phase commit.
For samples look under
$ORACLE_HOME/jdbc/demo/samples/oci8/jdbc20-samples/
null

Distributed Transaction in weblogic 5.1

Hi all,
Does Weblogic 5.1 support Distributed Transactions?.

While they aren't java-specific, if you're looking for XA/2PC details,
these 2 are good:
Transaction Processing: Concepts and Techniques (Morgan Kaufmann Series
in Data Management Systems)
by Jim Gray, Andreas Reuter
Principles of Transaction Processing
by Philip A. Bernstein, Eric Newcomer (Contributor)
5.1 does not support XA or 2 phase-commit. However, it does allow
multiple cluster members to enlist in the same transaction as long as
all database access goes through the same JDBC connection.
WLS 6.0 and later do support XA and 2PC.
-- Rob
chandrasekar wrote:
Hi all,
Does Weblogic 5.1 support Distributed Transactions?.Please suggest me some
books or documentation regarding Distributed Transactions, and about the XA compliant
resources.

Regarding Distributed Transactions

I am aware of JDBC transactions. Now while reading EJB i came to know that EJB supports Distributed Transactions.
My interpretation of Distributed transaction is
e.g.
Consider two CMT Beans A & B.
Bean-A contains a method foo() with a transaction attribute "Required".
Bean-B contains a method boo() with a transaction attribute "Required".
Now when a method "foo()" in a transaction calls method "boo()", the method "boo()" runs in the same transaction as "foo()". so here the transaction travels from "foo()" method to "boo()" method.
My Question: can i say the above is an example of Distributed transaction
Please let me know my interpretation is correct or wrong.
If wrong, please explain me in few words.

Hi Naresh,
Your interpretation is correct. Distributed transactions allow a transaction to propagate between
component invocations. Typically, this propagation occurs between components that are collocated
within the same JVM, but the propagation can also happen across JVMs, e.g. in the case of a
Remote EJB invocation.
--ken

Simulated distributed transactions in WLS5.1

Hello
          I can´t use WLS 6.0 I must use WLS 5.1. So I can´t to use distributed
          transactions.
          So that, my problem is this situation:
          Client code: in WL Personalization Server
          method
          UserTransaction.begin
          class1.create
          class2.updateDatabaseOracle1
          this.comit();
          Exception
          this.rollback();
          method commit
          class1.commit();
          class2.commit();
          UserTransaction.commit
          methdo rollback
          class1.rollback;
          class2.rollback;
          UserTransaction.rollback
          class1 in WL Personalization Server
          create
          EJBCreate
          commit
          EJB.putData
          rollback
          EJB.remove
          EJB in WL5.1
          I get this Error:
          "Connection has already been created in this tx context for pool
          named pool1. Illegal attempt to create connection from another
          pool: pool2"
          Can I modify the type of transaction in the EJB that solve this error??
          if the request is false How can I simulated it?
          I can lose the transanction because my class (class1) implements a
          rollback and commit methods that save it.
          Please Help
          Miguel Lopez Montero
          Soluziona Servicios Internet,Spain


<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC_TX ():
In the readme file of Oracle JDBC drivers 8.1.6.0.1 (http://technet.oracle.com/software/tech/java/sqlj_jdbc/files/Readme_01.txt)
it mentioned that it supports "distributed transactions".
As I understand, JDBC transaction is connection based and uses Oracle internal transaction manager. In order to do "distributed transactions", I must have at least two connections open at the same time each to its own database instance. How does the two connections coordinate the transactions? I thought in order to support "distributed transactions", one has to build a higher layer to encapsulate the two connections and therefore coordinate the distributed transactions. Any examples will be welcome.<HR></BLOCKQUOTE>
The two branches of the transaction are coordinated using 2-phase commit.
For samples look under
$ORACLE_HOME/jdbc/demo/samples/oci8/jdbc20-samples/
null

OLE DB provider 'MSDAORA' was unable to begin a distributed transaction

Hello!
I have following problem:
When I create a linked Server in MSSQL-Server 2000 with "Microsoft OLE DB Provider for Oracle" (MSDAORA) to Oracle 9.2i and try to create a transaction, i get following error message:
The operation could not be performed because the OLE DB provider 'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA' ITransactionJoin::JoinTransaction returned 0x8004d01b].
I also tried to use the "Oracle Provider for OLE DB", but with this provider i could even not get a connection to the Oracle Server. Error Message:
Error 7302: Could not create an instance of OLE DB provider 'OraOLEDB.Oracle'. OLE DB error trace [Non-interface error: CoCreate of DSO for OraOLEDB.Oracle returned 0x80040154].
Can anybody help me?
(sorry for my bad english)

I don't know if this is much help, but I came across this on the MS site:
http://support.microsoft.com/kb/280106
Message 9
Error 7391: The operation could not be performed because the OLE DB provider 'MSDAORA' does not support distributed transactions. OLE DB error trace [OLE/DB Provider 'MSDAORA' ITransactionJoin::JoinTransaction returned 0x8004d01b]
Verify that the OCI versions are registered correctly as described earlier in this article.
Note If the registry entries are all correct, the MtxOCI.dll file is loaded. If the MtxOCI.dll file is not loaded, you cannot perform distributed transactions against Oracle by using Microsoft OLE DB Provider for Oracle or by using Microsoft ODBC Driver for Oracle. If you are using a third-party provider and you receive Error 7391, verify that the OLE DB provider that you are using supports distributed transactions. If the OLE DB provider does support distributed transactions, verify that the Microsoft Distributed Transaction Coordinator (MSDTC) is running.

Settings for implementing Distributed Transaction

Hi ,
Can some one guide me as to what are the settings that need to be done on the Oracle client & server machine for implementing Distributed Transaction .
I have ODP.Net client 11 & Oracle Database Server 10g.
I read that I require Oracle Services for MTS to be installed on my system .
When I check the services installed on my machine ,I found OracleMTSRecoveryService (so i assume Oracle Services for MTS is installed on my system) .
I just can't figure out what part of settings I'm missing out ...
Please guide .
Many Thanks
Girija

Hello TeamIn,
Please check if you are in the 32/64 bit situation in think KB:
https://support.microsoft.com/en-us/kb/910907?wa=wsignin1.0 which is mentioned also in the link provided by David and you could confirm if there is 32/64 bit different version service on the
azure forum.
>>I am using Sql Server Express 2012 installed in an azure VM and App in Azure App services
I am not sure how the Windows Azure SQL Database is defined, you could confirm it on the azure forum if your database is already a Windows Azure SQL Database and if so, according to this
blog, it shows that the Windows Azure SQL Database does not support distributed transactions, which are transactions that multiple transaction managers (multiple resources).
Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Distributed Transactions HA and DR

We have a few SQL Server environments besides Biztalk and its speciall HA and DR configuration(SQL Server failover cluster and Biztalk Log Shipping) that use distributed transactions. Is there a HA or DR solution that supports distributed transactions
other than failover clustering? I am aware that database mirroring is not supported for distributed transactions. How about log shipping or replication? Is there any official documentation on this?
Thank you in advance

Hello,
As Shanky post, there is limitation of distributed transactions when using database mirroring or log shipping. When using Microsoft Distributed Transaction Coordinator (MSDTC) transactions, the local transaction coordinator has a resource ID that identifies
the server on which it is running. When a mirroring or log shipping failover occurs, the principal database becomes hosted on a different server (the mirroring partner or secondary server), and so the resource ID of the transaction coordinator is different.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Regarding distributed transaction

may be xi does not support distributed transaction. as 2 phase commit
really?
if yeah,and i have the question the following:
because as far as know, xi will create seperate transaction for each step.
and send step will influence the transactional behavior.
by checking help, i knew
we can set properties for send step not to start a new transaction.
can anybody tell me where to set that?
and then how can we assure transaction integrity.
if not 2 phase commit protocol, and with what to do it?

Hi ,
Please check this blog.
/people/sap.user72/blog/2005/10/15/jdbc-adapter-execution-mode-chained-or-unchained (JDBC Adapter execution mode Chained or Unchained )
Ranjeet Singh.

Error connecting SQL Azure - Network access for Distributed Transaction Manager (MSDTC) has been disabled

Sometimes I have an error connecting SQL Azure. The error occurs in an asp.net application and in a windows service running on VM in Azure. Error details:
System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network
access in the security configuration for MSDTC using the Component Services Administrative tool. ---> System.Runtime.InteropServices.COMException: The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT:
0x8004D024)
   at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel,
ITransactionShim& transactionShim)
   at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
   --- End of inner exception stack trace ---
   at System.Transactions.Oletx.OletxTransactionManager.ProxyException(COMException comException)
   at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
   at System.Transactions.TransactionStatePSPEOperation.PSPEPromote(InternalTransaction tx)
   at System.Transactions.TransactionStateDelegatedBase.EnterState(InternalTransaction tx)
   at System.Transactions.EnlistableStates.Promote(InternalTransaction tx)
   at System.Transactions.Transaction.Promote()
   at System.Transactions.TransactionInterop.ConvertToOletxTransaction(Transaction transaction)
   at System.Transactions.TransactionInterop.GetExportCookie(Transaction transaction, Byte[] whereabouts)
   at System.Data.SqlClient.SqlInternalConnection.EnlistNonNull(Transaction tx)
   at System.Data.ProviderBase.DbConnectionPool.PrepareConnection(DbConnection owningObject, DbConnectionInternal obj, Transaction transaction)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal&
connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
   --- End of inner exception stack trace ---
   at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
   at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection()
   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClassb.<GetResults>b__9()
   at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
   at System.Data.Entity.Core.Objects.DataClasses.EntityReference`1.Load(MergeOption mergeOption)
   at System.Data.Entity.Core.Objects.DataClasses.RelatedEnd.DeferredLoad()
   at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.LoadProperty[TItem](TItem propertyValue, String relationshipName, String targetRoleName, Boolean mustBeNull, Object wrapperObject)
   at System.Data.Entity.Core.Objects.Internal.LazyLoadBehavior.<>c__DisplayClass7`2.<GetInterceptorDelegate>b__2(TProxy proxy, TItem item)

Hello,
I am not an expert in MSDTC but as we know,SQL Azure Database does not support
distributed transactions. This means that SQL Azure doesn’t allow Microsoft Distributed Transaction Coordinator (MS DTC) to delegate distributed transaction handling.
One common cause of MSDTC getting involved in Entity Framework applications is the fact that we close and reopen the same connection as needed (i.e. for each query that is executed).To avoid the stack from opening and closing the connection multiple times,
you can simply open the connection explicitly and run the queries in the same connectio.
The following thread is about a similar issue, please refer to:
http://answers.flyppdevportal.com/categories/azure/sqlazure.aspx?ID=d705a8cf-cba4-494c-96f6-96a136bd29e3
What's more, you can also try the workaround that involves setting the Enlist option of the SQL Azure connection to false. For the detail explanation, please refer to:Entity
FrameWork and SQL Azure
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation. The documentation takes me windows 2008 R2 which is different than 2012!
Tired and trying to pick myself up off the floor!
Greg
Gman

In general, DTC is not required for SQL 2012. But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum. They would be more likely to know those situations where FTC might be needed by SharePoint.
.:|:.:|:. tim

ADF BC Support Distributed Transactions?

Similar Messages

Maybe you are looking for