Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dkimbrell
Starting Member
9 Posts |
 Posted - 2012-05-08 : 10:32:59
|
| I have an existing merge replicated database with about 55 tables, all with established relationships between each other. When this replication was originally setup, it was setup as row-level tracking. I need to change it to column level tracking. I manually changed the tracking type in the article properties, regenerated a snapshot, and synched, but the tracking type change does not work (even though it shows as column-level). I still get conflicts. I read that this is a known problem and that I have to drop all the tables from the publication and then add them back with column level tracking.I deselected all the tables from the publication, hit OK, then added them back with column level tracking (in the article properties dialog box), but now when I synch, I get an error message from the subscriber saying that it cannot drop tables because of foreign keys.How do I drop all the tables and re-add them with column level tracking? Can I do this through the Article Properties dialog boxes, I'm a novice and not sure what scripts to run in lieu of dialog boxes.OR - is there a way around this bug? A way I can change tracking type without having to drop and recreate all the tables?Thank you |
|
|
|
|
|
Change from row level to column level tracking