September 22, 2005 at 11:41 am
We currently have custom scripts that run .bat files to ship from 7.0 to 2000 and restore. All scheduled as jobs. Is anyone aware of a better or stable solution in getting this done. The scripts were written by a previous DBA and I dont totally agree on how he was doing it. Now that our 2000 server is being replaced I either need to use his method but would rather redo if possible. Any help would be appreciated. Thanks.
September 23, 2005 at 9:45 am
Don't know if this will help, but it's what we did back when:
- SQL 7.0 default instance on the "source" server
- SQL 7.0 default instance on the "target" server
- Standard Microsoft-supplied log shipping set up between the two; database restored in Standby mode so that the data was in read-only mode
- SQL 2000 named instance also on the "target" server
- Linked server definitions configured in SQL 2000 allowing it to access the Standby database on the 7.0 instance. (Since it's the same box, we had no "delegated authentication" issues.)
I think it was possible to do Microsoft log shipping from 7.0 to 2000, but the resulting database could not be set to Standby mode. (We eventually upgraded everything to SQL 2000.)
(Also, just to be clear, SQL 7.0 can only be installed as a default instance.)
Philip
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply