Hi to all,
I have a merge (pull) replication between SQL Server 2005 and SQL Server Express clients.
Data synchronisation is ok, and I already made some schema changes (like adding new columns) at the publisher database which were applied to the subscriber as they should.
Now this doesn't work anymore. New columns added at the publisher (with ALTER TABLE or Management Studio) are no longer replicated to the subscribers.
I don't get any error messages, and I can't find any hints in the logs why this has stopped working.
The "Replicate_Schema_Changes" is still set to TRUE (in general, none of the publication options had been changed).
I tried sp_enumeratependingschemachanges to find out any "bad changes" put the sp returns nothing.
I remember that the last thing I did was adding a default constraint, which was replicated successfully to the subscribers.
Can anybody help
Michael
Schema changes no longer replicated to subscribers
Donna M-T
One more thing - you must use TSQL to do your DDL statements, using SQL Management Studio is not supported/recommended. http://msdn2.microsoft.com/en-us/library/ms151870.aspx
zmy
Your post resembles a problem I am having.
I need to add two columns to 6 tables in my db. Of cousre this is after replication is in place and working.
Anyway, I ran sp_repladdcolumn <tablename>, <column name> <datatype>
The datatype will not take a length value.
It defaults to length of one. How to change
thxx..bt
Annie24372
Hi Mike,
I did test with a VMWare environment which is an exact copy of our production db server.
However, the test showed that the publisher looses knowledge about its subscribers after applying SP1. I still can see the subscribers in the replication monitor, but replication itselft with a subscriber is no longer possible. Even a re-initialization did not work.
A second test showed that schema changes still don't work. For those reasons we decided to completley remove the publication, apply SP1 and the post SP1 hotfixes, rebuild the publication and simply hope the best...
Michael
Lance Olson - MSFT
Maybe the following is a hint what might is wrong with my publication:
After adding a new column, I looked in SMS at publication properties - articles. The new column is listed there, but it is not checked. When I click on the column to include it in the publication, I get a message that the all subscriptions have to be reinitialized.
Question is, why is it suddenly neccessary to do a re-init
Debra Dove
We had the same problem. Removed the columns from the table (just the new ones), upgraded to SP1, and added the columns back in. This time it worked and the schema changes were replicated to the subscribers.
Hope that helps!
Mike
keajatthew