I'm very confused about the status (or future status) of the use of transactional replication. In several places on the MSDN pages I've seennotices that transaction replication is being depreciated and should not be used, but there is no recommendation about what I should replace it with. Yet in other places this type of replication is recommended as the best solution for a given scenario.
For example the following is suggested for a scenario similar to our situation: ms-help://MS.SQLCC.v10.SQLSVR.v10.en/s10rp_0evalplan/html/4b177aa2-2f76-43d2-8978-6bbd01b10337.htm (<mshelp:link filterstring="(("ProductVers"="kbsqlserv105")
OR ("DocSet"="NETFramework"))" keywords="6d676493-6ff9-4d5d-b752-af8b2f73cc6b">Overview
(Replication)</mshelp:link> > <mshelp:link filterstring="(("ProductVers"="kbsqlserv105") OR ("DocSet"="NETFramework"))" keywords="b6eaef99-471b-4782-ad3e-5db7177f1db1">Replicating Data
in a Server to
Server Environment</mshelp:link> > <mshelp:link filterstring="(("ProductVers"="kbsqlserv105") OR ("DocSet"="NETFramework"))" keywords="d58f6644-398c-4acb-b781-41538eb33bd8">Improving
Scalability and
Availability</mshelp:link> >)
Currently we are using SQL 2008 R2 STANDARD edition in our data centers but plan to migrate to SQL 2014 late this year (assuming Microsoft releases it sometime soon).
Our objective is to have 3 datacenters (Europe, N. America, Asia), each under normal operations serving there geographic region, but any one of them able to take over either as part of a load balance or fail-over (HA). We have a large number of web applications containing various mixtures of EF, LINC, and embedded SQL, with frequent use of multiple databases within a given SQL instance.
Given the above what would be the "best practice" recommendation implementation for our data network configuration?
Developer Frog Haven Enterprises