By Aaron Young - 4/4/2009
Hi,
When a DDT package is run against a database that is published for merge replication in SQL Server, the package removes all of the indexes and triggers that were added by SQL Server when the publication was setup. Effectively this means the merge replication has to be dropped and setup again.
Is there any way indexes and triggers whose names start with "MSmerge" can be left in place instead of deleting them? This would be a major win for anyone using replicated databases as it would allow the database to be altered without having to drop and re-publish.
On a similar note, it would be useful if a uniqueidentifier column could be added to the messaging and security tables as this would allow them to be included in the merge replication. Currently, SQL Server will add it's own uniqueidentifier columns to these tables but any future DDT package will try and remove them.
Thanks,
Aaron
|
|