We have a set of databases that are used together frequently from one solution (built using Entity Framework). We have views and stored procs that connect from one database to other databases in the same connection.
In SQL 2016 crossdatabase transactions are supported in an AlwaysON environment when the databases are located on different instances and thus in different availabilitygroups using different connectionstrings.
For us that configuration is not possible without a complete redesign of the software.
The only way we think we can make use of AG’s in SQL 2016 is to move all data from all databases to one single database, but that too costs a lot of effort.
Can you tell me the roadmap for cross-database transactions in future versions of SQL Server, or even in an upcoming servicepack of SQL 2016?
In case a future release will provide a solution or a good workaround we won’t need to change our application that much.
And maybe you can help us figure out a good alternative, maybe some handy functionalilty in the Entity Framework we are not yet using?
Thanks in advance,
Arash