Production Issue: Cannot Replicate data from SQL 2008 to SQL 2000

We are using Transactional Replication. I have data being pushed by multiple SQL 2000 Publication table into this one 2000 subscription table in SQL Server. Everything works fine. When I add the SQL 2008 Publication Table I get a lot of issues. I tried setting the synch to auto but the 2000 subscription would drop and be recreated which the other publication tables could not synch. I changed synch to replicate support only but the 2008 publication would throw out these types of errors The row was not found at the Subscriber when applying the replicated command.
vraj20Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ste5anSenior DeveloperCommented:
What topology? A mixed SQL Server 2000 and 2008 requires the correct topology and the correct service pack levels.

See Using Multiple Versions of SQL Server in a Replication Topology

SQL Server 2000 and SQL Server 2005 can both participate in replication topologies with SQL Server 2008. For SQL Server 2000 the minimum version is Service Pack 3 (SP3). For SQL Server 2005 the minimum version is Service Pack 2 (SP2).

When you replicate between or among different versions of SQL Server, you are usually limited to the functionality of the earliest version used. For example, if you upgrade a Distributor to an instance of SQL Server 2008, but you have a Publisher that is running an instance of SQL Server 2005 and a Subscriber that is running an instance of SQL Server 2000, you are limited to the general functionality and replication functionality of SQL Server 2000.

For all types of replication, the Distributor version must be no earlier than the Publisher version. (Frequently, the Distributor is the same instance as the Publisher.)

For transactional replication, a Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example, a SQL Server 2000 Publisher can have SQL Server 2008 Subscribers, and a SQL Server 2008 Publisher can have SQL Server 2000 Subscribers.

For merge replication, a Subscriber to a merge publication can be any version no later than the Publisher version. For more information about compatibility for earlier versions, see "Compatibility Level for Merge Publications" later in this topic. For more information about replication features that are supported in the various editions of SQL Server.
Vitor MontalvãoMSSQL Senior EngineerCommented:
vraj20, do you still need help with this question?
carlosmonteCommented:
Hi

I have a similar scenario and maybe sharing ideas can help.

I'm trying replication topology:
Publisher SQL 2000 SP4
Distributor and Subscriber SQL 2008
This topology should work according to docs.
But the snapshot agent fails to start I get login error. The distributor cannot connect to publisher. See attached.
We are testing with domain admin account so security should not be an issue.

I tried another topology to get more information
Publisher SQL 2000  SP4
Distributor SQL 2008
Subscriber SQL 2005 SP2
We get same error.

This topology worked
Publisher SQL 2005 SP2
Distributor SQL 2008
Subscriber SQL 2005 SP2

Then I read in the article:

Using a SQL Server 2005 or SQL Server 2008 Distributor with a Publisher Running SQL Server 2000
SQL Server 2005 and SQL Server 2008 can be used as a remote Distributor for Publishers that are running SQL Server 2000. To change agent properties in this scenario, execute the following stored procedures at the Distributor. These procedures let you change properties that were introduced in SQL Server 2005:
sp_MSchange_snapshot_agent_properties (Transact-SQL)
sp_MSchange_logreader_agent_properties (Transact-SQL)
sp_MSchange_distribution_agent_properties (Transact-SQL)
sp_MSchange_merge_agent_properties (Transact-SQL)

And from there I'm a little lost I must say. I am not a DBA :l

Any ideas?

*** If I should have asked the question myself I'll be happy to post itsnapshot agent errorThanks
CM

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
carlosmonteCommented:
Thank you Victor
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.