November 19, 2008 at 7:32 am
Hi,
we have 2 DB servers on different domains we need to let a client to get data from a view, located in one server, which is a join of data of two tables (double hop in linked server situation)
but since we cannot let domains trust each other, the client cannot read data of one server through another. I need to know if distributed transactions is a good choice for such situation.
any comment about what distributed transactions is, is also appreciated
November 19, 2008 at 7:58 am
Depending on what you need for security, the domains do not need to trust each other to have a linked server and a single view to handle your data need. You could use SQL authentication in the linked server and even connect via http to the second server if you had to.
A distributed transaction is primarily for updates. It is really to ensure an update is made across all necessary servers without any individual part failing. So, if you need to insert a new client on one server and an order for that client on another server in a single transaction, a distributed transaction will roll back the client insert if the order insert fails. MS uses the Distributed Transaction Coordinator (MS DTC) to handle this across multiple databases that can handle distributed transactions.
November 22, 2008 at 12:27 am
Thanks Michael for the comments,
From this article:http://www.sql-articles.com/index.php?page=articles/linked_server_part2.html], I concluded that SQL authentication will not resolve the problem, Please provide me with more comments if I'm wrong.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply