Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have SQL Server 2000 as publisher and SQL Server 20008 R2 as subscriber.

I want to replicate data from SQL Server 2000 to SQL Server 2008 R2 on a different machine.

Primary key fields are not defined on some tables so transaction replication is not a choice.

I think merge replication is not a choice because the Subscriber SQL Server version is higher than the publisher.

What can I do?

share|improve this question

migrated from Feb 7 '13 at 8:54

This question came from our site for professional and enthusiast programmers.

Can you not add primary keys to those tables which are missing them? – Damien_The_Unbeliever Feb 7 '13 at 8:19
I just can add an identifier filed and set it as primary key. Will this solve my problem for transactional replication? – Raymond Morphy Feb 7 '13 at 8:28
Well, you need primary keys on all tables for any replication to work. Otherwise how are you going to know which rows have been moved over to the subscriber or not? – Marian Feb 7 '13 at 10:03
May I ask what the business problem that you are trying to solve is here? I'm curious to know why Replication has been chosen as the solution implementation method over other available options, which could be more suitable. – John Sansom Feb 7 '13 at 14:15
I want to have an updated version of SQL Server2000 which is filled by windows applications in SQL server 2008 and use it in my website. because I have used some features of SQL server 2008 in my web site.I just can add add identity fields as primary key in this solve my problem? – Raymond Morphy Feb 8 '13 at 21:03

Bad news: SQL Server 2000 isn't officially supported. You're putting yourself in a situation where the link between these two servers could cause problems, and if you call Microsoft for support, you'll be out of luck.

Don't be That Guy who breaks the production server because he wanted to connect these two servers. Tell your management that SQL Server 2000 is out of support. SQL Server 2008 R2 has lots of cool features to help - rather than working with replication in an unsupported scenario, put your time into getting that old SQL Server 2000 box into a supported scenario.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.