Replication from 2005 to 2000

  • We currently have a rather large database running on SQL 2000. This database receives and stores ELR's electronic lab reports. They are inserted twice a day in rather large batch files. These batch files are received on a server, translated and inserted into the SQL 2000 database on a second server. For the most part the client has read only privileges on this database but there are a few changes made.

    What I would like to do is add a SQL 2005 database on the first server that receives the ELR's, translates the ELR and insert them into the SQL 2005 database that is then replicated to the second server with the SQL 2000 database. This would allow me to make changes and updates on the SQL 2005 server/database without interruption of the SQL 2000 server/database. Any idea or suggestions?

  • can you not get the data and have it replication both to your 2005 and 2000 server.

    use your 2005 server for testing while your 2000 keeps plowing thru.

    -----------------------------
    www.cbtr.net
    .: SQL Backup Admin Tool[/url] :.

  • Currently we receive electronic lab record from several commercial labs. The records are received as a batch at night. They are in a HL7 2.3.1 format. They are translated XML and inserted into a SQL 2000 Database on a second server.

    What I want to do is receive, translate and insert into a SQL 2005 database on the first sever. This server would hold messages in a number of databases. Replication would then occur between the database on the first sever and several different servers. The current second server, SQL 2000 is available to a number of clients as read only. Occasionally they will need to make changes to the publisher database. This would allow us to shut down server one without affecting the second server and client interaction.

Viewing 3 posts - 1 through 2 (of 2 total)

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