| Groups | Blog | Home |
sql server replication : Upgrading publishers to 2005 (4 questions) sorry i know this isn't a consulting fourm.
install sql over itself and let it handle the upgrade process. (do you have to reinitialize publications?) 2. If i upgrade my publisher to 2005 will I need to also upgrade my distributors (these are separate machines on our network)? If so, will this cause reinitialization? 3. Can any of this be done without having to reintialize 4. Can your subscriber still be 2000 even though your publisher is now upgraded to 2005. Thanks Paul, Hilary, or anyone for their response.
It requires a new snapshot for merge. I don't know about transactional or
its variants. Do the distributor first. Your subscribers can be SQL 7, 2000, and 2005. Jet subscribers are no longer supported. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Combfilter" <myusenetnym@hotmail.com> wrote in message news:MPG.1e80b4334c9ec8c6989686@news.newsreader.com... > 1. Has anyone here done an 'inline server upgrade' . basically you > install sql over itself and let it handle the upgrade process. (do you > have to reinitialize publications?) > > 2. If i upgrade my publisher to 2005 will I need to also upgrade my > distributors (these are separate machines on our network)? If so, will > this cause reinitialization? > > 3. Can any of this be done without having to reintialize > > 4. Can your subscriber still be 2000 even though your publisher is now > upgraded to 2005. > > Thanks Paul, Hilary, or anyone for their response. > > -comb
1) You can also try to use the proc sp_vupgrade_replication to upgrade
replication databases other than 'inline server upgrade'. 2) If you upgrade the publisher to 2005, you need to upgrade the distributor too. Quote from Upgrading Replicated Databases http://msdn2.microsoft.com/en-us/library/ms143699.aspx a.. 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.. A Publisher can be any version as long as it less than or equal to the Distributor version. a.. Subscriber version depends on the type of publication: a.. 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 running can have SQL Server 2005 Subscribers; and a SQL Server 2005 Publisher can have SQL Server version 7.0 Subscribers. b.. An updatable Subscriber to a SQL Server 2005 transactional publication can be any version equal to or greater than Microsoft SQL Server 2000 SP3. c.. A Subscriber to a merge publication can be any version less than or equal to the Publisher version. Yi Chen [quoted text, click to view] "Combfilter" <myusenetnym@hotmail.com> wrote in message news:MPG.1e80b4334c9ec8c6989686@news.newsreader.com... > 1. Has anyone here done an 'inline server upgrade' . basically you > install sql over itself and let it handle the upgrade process. (do you > have to reinitialize publications?) > > 2. If i upgrade my publisher to 2005 will I need to also upgrade my > distributors (these are separate machines on our network)? If so, will > this cause reinitialization? > > 3. Can any of this be done without having to reintialize > > 4. Can your subscriber still be 2000 even though your publisher is now > upgraded to 2005. > > Thanks Paul, Hilary, or anyone for their response. > > -comb
1. Yes, many of them. I did 3 of these with CTP16, 2 more with RC1, 1
additional with RC2, and about a dozen with the gold code. One that I'm working through right now is my biggest which is going to take a few months to complete since we have to upgrade almost 3000 servers and nearly 15000 mobile clients. Reinitialization wasn't required. For the large one I'm working on now, we are taking the opportunity to also roll out a major upgrade to the database and do a bunch of clean-up work, so we are completely rebuilding everything as we go. 2. The distributor is always the FIRST thing that gets upgraded, then subscribers, then finally the publishers. Yes, you have to upgade the distributors. No, it does not force reinitialization. 3. See 1 & 2 above 4. Yes, the subscriber can be 2000 if the publisher is 2005. -- Mike http://www.solidqualitylearning.com Disclaimer: This communication is an original work and represents my sole views on the subject. It does not represent the views of any other person or entity either by inference or direct reference. [quoted text, click to view] "Combfilter" <myusenetnym@hotmail.com> wrote in message news:MPG.1e80b4334c9ec8c6989686@news.newsreader.com... > 1. Has anyone here done an 'inline server upgrade' . basically you > install sql over itself and let it handle the upgrade process. (do you > have to reinitialize publications?) > > 2. If i upgrade my publisher to 2005 will I need to also upgrade my > distributors (these are separate machines on our network)? If so, will > this cause reinitialization? > > 3. Can any of this be done without having to reintialize > > 4. Can your subscriber still be 2000 even though your publisher is now > upgraded to 2005. > > Thanks Paul, Hilary, or anyone for their response. > > -comb
A new snapshot is generated for merge. It does NOT force reinitialization.
-- Mike http://www.solidqualitylearning.com Disclaimer: This communication is an original work and represents my sole views on the subject. It does not represent the views of any other person or entity either by inference or direct reference. [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:O5rwA55RGHA.4952@TK2MSFTNGP09.phx.gbl... > It requires a new snapshot for merge. I don't know about transactional or > its variants. Do the distributor first. Your subscribers can be SQL 7, > 2000, and 2005. Jet subscribers are no longer supported. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > > > > "Combfilter" <myusenetnym@hotmail.com> wrote in message > news:MPG.1e80b4334c9ec8c6989686@news.newsreader.com... >> 1. Has anyone here done an 'inline server upgrade' . basically you >> install sql over itself and let it handle the upgrade process. (do you >> have to reinitialize publications?) >> >> 2. If i upgrade my publisher to 2005 will I need to also upgrade my >> distributors (these are separate machines on our network)? If so, will >> this cause reinitialization? >> >> 3. Can any of this be done without having to reintialize >> >> 4. Can your subscriber still be 2000 even though your publisher is now >> upgraded to 2005. >> >> Thanks Paul, Hilary, or anyone for their response. >> >> -comb > >
Why does subscriber have to be upgraded?
In article <#arMbaFSGHA.4952@TK2MSFTNGP09.phx.gbl>,
mike@solidqualitylearning.com says... [quoted text, click to view] > 1. Yes, many of them. I did 3 of these with CTP16, 2 more with RC1, 1 Thanks so much for your response. This answers all of my questions. > additional with RC2, and about a dozen with the gold code. One that I'm > working through right now is my biggest which is going to take a few months > to complete since we have to upgrade almost 3000 servers and nearly 15000 > mobile clients. Reinitialization wasn't required. For the large one I'm > working on now, we are taking the opportunity to also roll out a major > upgrade to the database and do a bunch of clean-up work, so we are > completely rebuilding everything as we go. > > 2. The distributor is always the FIRST thing that gets upgraded, then > subscribers, then finally the publishers. Yes, you have to upgade the > distributors. No, it does not force reinitialization. > > 3. See 1 & 2 above > > 4. Yes, the subscriber can be 2000 if the publisher is 2005. > > Damn you sound like you have a huge project ahead of you. 3000 servers. I was bitching because we have 6 distributors and 20 publishers. Glad I am not in your shoes.
In article <exNWbaFSGHA.4952@TK2MSFTNGP09.phx.gbl>,
mike@solidqualitylearning.com says... [quoted text, click to view] > A new snapshot is generated for merge. It does NOT force reinitialization.
> >
In article <MPG.1e80b4334c9ec8c6989686@news.newsreader.com>,
myusenetnym@hotmail.com says... [quoted text, click to view] > 1. Has anyone here done an 'inline server upgrade' . basically you
> install sql over itself and let it handle the upgrade process. (do you > have to reinitialize publications?) > > 2. If i upgrade my publisher to 2005 will I need to also upgrade my > distributors (these are separate machines on our network)? If so, will > this cause reinitialization? > > 3. Can any of this be done without having to reintialize > > 4. Can your subscriber still be 2000 even though your publisher is now > upgraded to 2005. > > Thanks Paul, Hilary, or anyone for their response. > > -comb
Two rules to follow.
Upgrade order must be Distributer, Subscriber, Publisher. Always stop replication agents during the upgrade. Make sure there is nothing in the distribution queue during the upgrade process. These two rules should handle 90% of your transactional replication upgrade issues. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Combfilter" <myusenetnym@hotmail.com> wrote in message news:MPG.1e80b4334c9ec8c6989686@news.newsreader.com... > 1. Has anyone here done an 'inline server upgrade' . basically you > install sql over itself and let it handle the upgrade process. (do you > have to reinitialize publications?) > > 2. If i upgrade my publisher to 2005 will I need to also upgrade my > distributors (these are separate machines on our network)? If so, will > this cause reinitialization? > > 3. Can any of this be done without having to reintialize > > 4. Can your subscriber still be 2000 even though your publisher is now > upgraded to 2005. > > Thanks Paul, Hilary, or anyone for their response. > > -comb
Technically, it doesn't have to be upgraded. I assumed you were upgrading
all SQL Servers in the topology. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Ken" <kshapley@sbcglobal.net> wrote in message news:1142456366.822204.26970@j33g2000cwa.googlegroups.com... > Why does subscriber have to be upgraded? >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
October 2008
| home · blog · groups | Questions? Comments? Contact the dn |