My colleagues and I have to migrate a database from SQL Server 2008 R2 to SQL Server 2012.
Schema, triggers, stored procedures etc. are working fine. But we also have to "migrate" the replication mechanism.
Replication is used to transfer data from the intranet to the dmz and vice versa. (There can be edits on both sides!!)
At the moment we use transactional replication with updatable subscribers. The problem is: this mechanism isn't available in SQL Server 2012 any more.
Question: what is my best option to replace that feature?
Requirements:
- Internal and external database can be edited
- Near "real time". Maximum time until the edits show up in the other database sould be around 10 minutes.
- Due to restrictions from the clients security team the connection attempts between databases may only be initiated from the internal database.
If I am correct Microsoft advises to use peer to peer replication as a replacement, but I am not sure that we can use that because of the security restriction.
Read/Write speed is not our first concern because there are only ~3000 users. The application uses Entity Framework 4.5 (if that matters).
Any advice will be appreciated!