asked
how to implement distributed database in SQL?
hii..i need to implement distributed database over the systems.can u please guide me how to design distributed database in SQL on which i will able to perform transactions simultaneously.
That is an amazingly broad area to cover with an answer on this website. If you are talking about synchronous commits across multiple updateable nodes, then you are out of luck in terms of native support. If you want to have multiple nodes with a single writeable master node, then you could look into [AlwaysOn Availability Groups][1] If you really need distributed writeable nodes, then [Peer 2 Peer Transactional Replication][2] would be the only option that is native to SQL Server, but that doesn't offer any support for synchronous commits across the nodes, you only get "eventual consistency". [1]:
http://msdn.microsoft.com/en-us/library/ff877884.aspx [2]:
http://msdn.microsoft.com/en-us/library/ms151196.aspx
hello William sir,i am realy thankful to u to suggest me useful material related to my study.i had read Peer 2 peer replication ,that scale out read operation .but my mainly work is on serializabilty of transactions and handle the conflict among the transactionsoperation both (READ-WRITE).can u pleaze tell me that is it possible to implement serilizabilty aglorithm over distributed environment using SQL.
You may also want to look at [Federated Databases][1] and [sharding][2] with [Azure SQL Databases][3]. This is a mechanism to easily expand or contract your storage needs on the fly. [1]:
http://msdn.microsoft.com/en-us/library/windowsazure/hh597452.aspx [2]:
http://social.technet.microsoft.com/wiki/contents/articles/how-to-shard-with-sql-azure.aspx [3]:
http://msdn.microsoft.com/en-us/library/windowsazure/ee336279.aspx
13 People are following this question.
