by Hi all,
Recently we made some necessary database changes to our production
database(SQL Server 7.0 running on windows NT) to facilitate an
upgrade to our in-house designed Information System. Due to the need
for mobile users we had implemented merge replication with pull
subscriptions some time ago and have continued quite successfully
(only a couple of hiccups !) for the last year. However, this time
when we dropped replication (using all of the required stored
procedures through Query Analyzer) replication did not seem to clean
up properly. A number of triggers were left on the replicated tables
such as old del_234E… , ins_234E…, upd_234E. These
triggers then caused conflicts when synchronising as the views these
triggers reffered to had been cleaned up by the stored procedures. A
bit of a mess really ! We managed to resolve this by dropping the
conflicting triggers from the production database and then from all of
the pull subcribers databases. So far things have been running
smoothly but we are concerned this may not have been the right thing
to do !
Has anyone else had this problem, any feedback would be most
appreciated.
Thanks in advance
Andrew