SQl 2000 with SQL 7 standby

  • Hi - we've finally decided to move our production environment to SQL 2000. However, I have to maintain a realtively warm standby server using SQL 7.0 just in case the new system goes pear shaped during the first couple of weeks. My idea was to use log shipping from the production server to another SQL 2000 system (initial_Standby) . On the initial_standby box, I'll have a DTS job to copy all the data into existing blank tables on a SQL 7 box which is the true standby. How does this sound as a framework? I have assumed that you can't restore SQL 2000 databases onto SQL 7, even with the appropriate compatability level - is this correct? Has anyone else had to do something similar, and if so how did they do it? Thanks.

    Paul Ibison

    Paul.Ibison@btinternet.com


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • That sounds ok to me.

    Andy

  • Thanks, Andy - nice to know I'm on the right track. One final question though: I intend to use log shipping between the 2 SQL 2000 boxes, and I know I'll need Enterprise edition on the 'Publisher', but do I need Enterprise Edition on the 'Subscriber' also?

    Paul Ibison

    Paul.Ibison@btinternet.com


    Paul Ibison
    Paul.Ibison@replicationanswers.com

  • Note You cannot implement log shipping between two instances of SQL Server 2000 if one part of the log shipping pair is not an Enterprise Edition installation. Log shipping can be set up between SQL Server version 7.0 with Service Pack 2 installed and SQL Server 2000 (see "Log Shipping Interoperability Between SQL Server 7.0 and SQL Server 2000" later in this chapter).

    from http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/sql/reskit/sql2000/part4/c1361.asp

    Steve Jones

    steve@dkranch.net

  • Speaking of log shipping... I having a heck of a time setting this up, manually, on a SQL 7.0 server. Problem is probably not SQL related, but any ideas would be appreciated. The problem is that the the standby server is off-site, connected via T-1, and the transaction volume is such that I can't get the T-Log backup copied over in time. In a 1/2 period, for example, I had 250 MBs of activity, and it took more than a 1/2 took copy the t-log backup. Any tools or ideas?

  • Saaber,

    Did find any solution, I am having the same issue

Viewing 6 posts - 1 through 5 (of 5 total)

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