vraj20
asked on
Replicate many SQL 2008 tables to one 2000 subscription
We currently have replication turned on where many 2000 tables are pushing to one 2000 subscription table. Everything works fine until we tried to replicate data from 2008 to 2000. When the 2008 publication drops and recreates the table it causes everything to fail
ASKER
The Subscription Table is in SQL 2000
The Publication Table is in SQL 2008
When we turn on replication and create a new snapshot for SQL 2008 Table. The Subscription Table gets drop and gets recreated and all the published tables from SQL 2000 returns with an error message that it can not find the records in the Subscription table
SubscriptionTable.txt
PublishTable.txt
The Publication Table is in SQL 2008
When we turn on replication and create a new snapshot for SQL 2008 Table. The Subscription Table gets drop and gets recreated and all the published tables from SQL 2000 returns with an error message that it can not find the records in the Subscription table
SubscriptionTable.txt
PublishTable.txt
Ok this does not data type issue. i again read out your question.
You have sql 2008 replication pointing to one subscription table (sql 2000) and another sql 2000 publication is also pointing to same subscription.
If this is the case table in the subscription has been overwritten from sql 2008 data thats why you are getting error in sql server 2000 publication.
Did you set the sync property to auto while setting up sql 2k8 replication.
You have sql 2008 replication pointing to one subscription table (sql 2000) and another sql 2000 publication is also pointing to same subscription.
If this is the case table in the subscription has been overwritten from sql 2008 data thats why you are getting error in sql server 2000 publication.
Did you set the sync property to auto while setting up sql 2k8 replication.
ASKER
Where can I set the synch property
ASKER
By default is the synch property set to auto
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I will try this and let u know
vraj20, do you still need help with this question?
I would suggest, migrate 2000 databases to 2008 or 2012.