Comments
Sort by recent activity
I am having this issue with 13.1.1.5299. It means we manually have to run upgrade scripts involving changes to UDTs. / comments
I am having this issue with 13.1.1.5299. It means we manually have to run upgrade scripts involving changes to UDTs.
I switched to just using basic transactional replication with our secondary location just acting as a backup and in this configuration sqlcompare works. It appears that it's only when using peer-to-peer that this problem arises. The column mentioned in the error "$sys_p2p_cd_id" is used by peer-to-peer replication for conflict resolution. So I don't think sql compare should be having anything to do with this column. It is however a big issue for us as we do want to use P2P replication and we should at least be able to generate an upgrade script whilst replication is running which we can't at the moment by the looks of things.
cheers,
Huw / comments
I switched to just using basic transactional replication with our secondary location just acting as a backup and in this configuration sqlcompare works. It appears that it's only when using peer-to...