New answers tagged transactional-replication
Replication normally works and I have not encountered any issues where I have to create an additional index on the distribution database. (In my company we use replication a lot for doing data movement from one region to another) If you are not having problems with Replication, then avoid creating those indexes. Index creation is not FREE, since SQL Server ...
The only way I can think of doing this is to slightly hack the process. It would involve the following steps: Copy the Distribution agent job and rename it to indicate it is run manually. You'll also need to change/disable the schedule and remove the "-Continuous" flag from the exec command of this new job. Create a job that does the following: Step 1: ...
This should work as it did for me: Set the -failoverpartner using the mirror name in the sql agents for replication. Fail mirror over to secondary Make sure replication continues to send commands to subscriber. Remove mirroring so primary is no longer connected. Go to distributor, add an alias (sql server alias) The alias should be the old principal name ...
What about putting the Distributor in an AlwaysOn Availability Group of it's own on two different servers and make the secondary a synchronous replica? Besides, there's real benefit in a high volume OLTP environment to not having the Distributor on the same SQL Server.
Top 50 recent answers are included