Is it safe to change the replicate schema property of a publication mid-stream? We have a server that rarely gets schema changes to the published table, but once a year or so the vendor might change the underlying table(s) in the publication. This is usually
a field size change and/or adding a new field.
I don't want to take any chances on disrupting the current merge publication since hundreds of users are already syncing their subscriptions daily. And the sqlce database file is very large (1gb) so it's not practical to have them all reinitialize their
The application using the replica databases will not need the majority of these changes, but at least one of the fields that is being altered in size is already part of the publication. Am I right in assuming that this will 'break' the subscriptions anyway?
View Complete Post