We have a primary web/database server (SQL Server 2012) which publishes data to our backup web/database server (also SQL Server 2012) subscriber using transaction replication. We want to be able to direct users to the backup server in case the primary
server fails but writing to the subscription database directly from the website on the backup server throws a "cannot insert a duplicate key" error. I've read that this is by design and I've also read that "Updateable Subscriptions" was
deprecated on SQL Server 2012. Since we cannot afford to purchase the Enterprise Edition, we are looking for an inexpensive/easy way to do this. I'm wondering if deleting the local subscription on the backup server would cause the identity field value to correct
increment from the last value written during the replication. And I'm wondering if once the primary server is repaired if it would be possible to backup/restore the database from the backup server to the primary server. Any help would be appreciated.
↧