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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-03-07 : 07:41:04
|
| Jim writes "We are running replication on a backup SQL server for redundancy (NT 4.0 O.S. SQL Server 2000). Using a constant merge Push from the primary server to keep the files current. Because we had to make some changes to table Structure and add columns. The service was Dropped the changes were made and the service was recreated. On Creation of the new merge I noticed that the new snapshot had not reflected the Table changes to the backup SQL server. On input of data to the primary table, The merge crashed and gave a warning that the Structure of the primary and backup was not compatible. I deleted the merge and went to manually copy the Primary table over to the backup however the Backup would not allow me to delete or modify the table stating it was being used for replication……. Sure enough on the Backup SQL server there is not only 1 but 2 orphaned Replication subscriptions. I have found no documentation on how to deal with this condition. How can I fix this and prevent it from happening in the future. We are currently changing all data storage to SQL and redeveloping the font ends. We need the redundancy of the merge but will have to make Table changed often as the development progresses." |
|
|
|
|
|
Modifications to Tables While useing merge Replication