Post reply

Replication from 2K5 to 2K?

  • June 27, 2006 at 8:53 am

    #169317

    Does anyone know if it is possible to replicate from SQL2K5 to SQL2K (and maybe back again)?

    I know it is possible to go from 2K to 2K5, but I've not been able to find any clear info on doing it the other way.

    Thanks,

    Mark.

  • June 28, 2006 at 5:58 am

    #646335

    It is possible to do both. You must add the SQL 2k box as a subscriber in Managment Studio to be able to do this.

  • June 28, 2006 at 7:55 am

    #646356

    Excellent. Thanks for that.

    I'll give it try soon - we will be bringing in some 2K5 boxes soon, and I wanted to avoid any obvious problems before they have the opportunity to cause any trouble.

    Regards,

    Mark.

  • June 28, 2006 at 11:50 am

    #646431

    Depends on the type of replication.  Merge replication isn't supported from SQL 2000 to SQL 2005

    SQL Server Versions Supported

    Microsoft SQL Server version 7.0 service pack 4 (SP4) is the minimum version required to participate in a replication topology with SQL Server 2005. If you use SQL Server 2000, service pack 3 (SP3) is required. If you have more than one version of SQL Server in a replication topology:

    • A Distributor can be any version as long as it is greater than or equal to the Publisher version (in many cases the Distributor is the same instance as the Publisher).
    • A Publisher can be any version as long as it less than or equal to the Distributor version.
    • Subscriber version depends on the type of publication:

      • A read-only Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server version 7.0 Publisher can have SQL Server 2005 Subscribers; and a SQL Server 2005 Publisher can have SQL Server version 7.0 Subscribers.
      • An updatable Subscriber to a SQL Server 2005 transactional publication can be any version equal to or greater than Microsoft SQL Server 2000 SP3.
      • A Subscriber to a merge publication can be any version less than or equal to the Publisher version.

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

  • June 29, 2006 at 1:52 am

    #646566

    Yep, that makes things clearer.

    Thanks for your help.

    Mark.

  • July 15, 2006 at 4:16 pm

    #649421

    I LOVE THIS WEBSITE!!!!!!!!!!!!!!!!!

    Thank you for your post SRB.

  • July 18, 2006 at 1:41 am

    #649720

    Make sure that the compatibility level of Database, In Database properties should be defined for use of lower version then SQL 2005

    80 for using SQL 2000

    70 for using SQL 7.0

     

    Arfat Chougulay

  • July 18, 2006 at 3:21 pm

    #649971

    Actually I didn't find I had to adjust the compatibility level, but then again I'm doing read only transactional replication.

    There is another thing though: If you want to replicate tables with user defined types (and you are having the distributor set up on 2k5) to 2k it will fail. The snapshot scripts want to use the 2k5 syntax for creating the UDT which 2k doesn't understand. So make sure you map UDT's to simple types (an option in the article settings).

    Cheers,

    Guido

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply