Duplicate publication created on failover of Always on HA

[JonathanH]

I'm currently doing some testing using Qlik replicate for change capture from an Always on HA MSSQL server source.  I've followed recommendations and setup a separate distribution server, and redirected the original publisher to the AG listener.

Everything seems to work fine except when I failover to another replica in the availability group a duplicate publication is created with a 1 digit increment in the name.  If I manually create a publication on the primary replica and failover this doesn't happen, so it does appear to be something related to Qlik rather than the replication configuration.

I don't think it will cause an issue having 2 identical publications (except the name of course), but I want to reduce load on the source system as much as possible.  Would having two log reader agents running doing the same task cause a problem?

Has anybody come across this before, and if so did you manage to stop it creating a duplicate publication after failover?

[Heinvandenheuvel]

I don't think articles themself are overhead. They are a flag to indicate to the Tlog creation process to bring along more (PK) than just the barebones needed for recovery. That's when the work happens, but not twice.

Best I know, that number in the publication corresponds with the dbid. Please check with for example:  select db_name(), db_id(db_name()) .

Hein.

[PGN · Accepted solution]

This happens, especially when you fail over.  The Publication Articles will most likely clear out on the secondary nodes.  You can delete them if you like, or just let them go.  Also, when it switches back, if the existing publication is there, it will create a new one...example from one of my DBs.  The number may start out as the DBID, but subsequent creations appear to be arbitrary. 

[JonathanH]

Thanks for responding that's exactly the same behaviour I am seeing.  As long it's not just occurring on my setup then I'll just expect an additional publication to be created on failover, it doesn't appear to cause any issues.