Re: Upgrade scenario
- From: "Tom" <mcseman@xxxxxxxxxxx>
- Date: Fri, 6 Jan 2006 09:34:04 +0100
Thank you both for your quick replies. Your sugestions seam OK. I was hoping
that something similar could be done.
I will test that scenario in my test environment first and see how it
goes...
Thanks
Tom
"Michael Hotek" <mike@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eM4pz8oEGHA.1312@xxxxxxxxxxxxxxxxxxxxxxx
> The archiecture you are describing is impossible. You can not use merge
> replication between SQL Server 7.0 and SQL Server 6.5. SQL Server 6.5
> also does not support transactional with immediate updating subscribers
> (only other updateable option in SQL Server 7.0).
>
> So, disregarding what you have listed as your current architecture, you
> can do the following process regardless of replication method you have
> deployed.
>
> 1. Install 1 new server with Windows 2003 and SQL Server 2005
> 2. Transfer all logins from the 7.0 server to the 2005 server
> 3. Recreate any SQL Agent jobs that should be setup on the 2005 server
> 4. Enable replication and set this machine up as a distributor.
> 5. Create a new merge subscription from SQL Server 7.0 to SQL Server 2005
> 6. Script out any objects, in 7.0 that did not get created on the 2005
> database
> 7. Create a new publication on SQL Server 2005 (distributor is what was
> set in step 4)
> 8. Drop the subscription to the first 6.5 database and recreate the
> subscription from the publication created in step 7
> 9. Repeat step 8 for each additional 6.5 subscriber
>
> You now have your existing 7.0 server publishing to SQL Server 2005
> through the 2005 distributor. You have moved all of your subscribers over
> to receiving their data from the new SQL Server 2005 server.
>
> 10. Drop the 7.0 publication and subscription.
>
> You now have 1 new server with Windows 2003 and SQL Server 2005 deployed
> as your publisher and distributor. Everything else is still sitting
> exactly as it was before. The interesting thing at this point, is that
> you incurred no dowtime on your applications and everything was
> transferred to the new SQL Server 2005 instance running on your new
> Windows 2003 Server. Now you just incrementally complete the process.
>
> 11. Deploy your second Windows 2003/SQL Server 2005 server, create a new
> subscription
> 12. Once you have verified that everything works correctly, eliminate one
> of the 6.5 subscribers and point any applications that were using it to
> the server deployed in step 11.
> 13. Repeat step 12 for each subscriber
>
> By doing this you get the following:
> 1. Incremental upgrade
> 2. Applications congtinue to run during the upgrade
> 3. Minimal, if any downtime
> 4. Complete replacement of 7.0 and 6.5 without carrying any legacy
> binaries
> 5. Multiple upgrades not required
>
> Now if you were not deploying new servers, then this process would be
> modified by upgrading the OS on all servers to Windows 2003 as the first
> step in the process. Instances of SQL Server 2005 would be installed
> side-by-side with the previous version. Everything else would remain the
> same.
>
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "Tom" <mcseman2002@xxxxxxxxxxx> wrote in message
> news:OAMPS9kEGHA.2012@xxxxxxxxxxxxxxxxxxxxxxx
>> Current situation:
>> - 1 central location running SQL 7.0 acting as a publisher and
>> distributor in merge replication
>> - 30 remote locations running SQL 6.5 and acting as subscribers
>> - subscribers are pushing articles to central location twice a day
>>
>> We are planning to replace all servers with new ones running windows 2003
>> and SQL 2005.
>> There is no way we can replace all servers and migrate the databases over
>> night so we need a scenario where we can replace remote servers one by
>> one and to ensure that old and new remote locations can replicate with
>> central location at the same time....
>> any suggestions??? Thanks
>>
>> Tom
>>
>>
>
>
.
- References:
- Upgrade scenario
- From: Tom
- Re: Upgrade scenario
- From: Michael Hotek
- Upgrade scenario
- Prev by Date: Re: cannot delete subscriptions
- Next by Date: Re: Auto Create trigger after re-initialization completed
- Previous by thread: Re: Upgrade scenario
- Next by thread: Partial config on a non-replicating DB?
- Index(es):
Relevant Pages
|
