2 deleted 61 characters in body
source | link

CrossIn SQL Server 2014, memory-database queries are distributed transactions and handled by DTC.
Dooptimized tables do not use distributedsupport cross-database transactions unless you need to. The use of distributed transactions can adversely impact performance and response time, because of the additional work that Microsoft DTC (MSDTC) needs to do to executeYou cannot access another database from the two-phase commit protocol to ensuresame transaction or the ACID properties. These cansame query that also be difficult to debugaccesses a memory-optimized table. Debugging distributed transactions can be complex and inYou cannot easily copy data from a distributed environmenttable in one database, networking related issues can create additional complexity and generate performance and availability problemsto a memory-optimized table in another database.http://msdn.microsoft.com/en-us/library/dn584627(v=sql.120).aspx Distributed and cross-database transactions are not supported for database mirroring/AOAG. http://technet.microsoft.com/en-us/library/hh393530.aspx. If you are going to use ownership chaining, be aware of the security risks http://msdn.microsoft.com/en-us/library/ms188676.aspx

Cross-database queries are distributed transactions and handled by DTC.
Do not use distributed transactions unless you need to. The use of distributed transactions can adversely impact performance and response time, because of the additional work that Microsoft DTC (MSDTC) needs to do to execute the two-phase commit protocol to ensure the ACID properties. These can also be difficult to debug. Debugging distributed transactions can be complex and in a distributed environment, networking related issues can create additional complexity and generate performance and availability problems. Distributed transactions are not supported for database mirroring/AOAG. http://technet.microsoft.com/en-us/library/hh393530.aspx

In SQL Server 2014, memory-optimized tables do not support cross-database transactions. You cannot access another database from the same transaction or the same query that also accesses a memory-optimized table. You cannot easily copy data from a table in one database, to a memory-optimized table in another database.http://msdn.microsoft.com/en-us/library/dn584627(v=sql.120).aspx Distributed and cross-database transactions are not supported for database mirroring/AOAG. http://technet.microsoft.com/en-us/library/hh393530.aspx. If you are going to use ownership chaining, be aware of the security risks http://msdn.microsoft.com/en-us/library/ms188676.aspx

1
source | link

Cross-database queries are distributed transactions and handled by DTC.
Do not use distributed transactions unless you need to. The use of distributed transactions can adversely impact performance and response time, because of the additional work that Microsoft DTC (MSDTC) needs to do to execute the two-phase commit protocol to ensure the ACID properties. These can also be difficult to debug. Debugging distributed transactions can be complex and in a distributed environment, networking related issues can create additional complexity and generate performance and availability problems. Distributed transactions are not supported for database mirroring/AOAG. http://technet.microsoft.com/en-us/library/hh393530.aspx