Hilary / Paul 2. questions.

1. I need to upgrade to sp3a on a distributor
that has about 40 publications to various
subscribers. I will be going from sql2k rtm to
sql2k sp3a. Are there any issues as far as
replication goes patching from rtm to sp3a? I
cannot afford to reinitilize any of these
publications.
2. Is there like a file size limit on using the
compress feature of a snapshot? I was able to
compress a 1gb table fine, but when I tried a
10gb one it always fails with a time out.
tia
-comb
btw, Hilary I just ordered your book for
45bucks.. hope it helps.
1. There are not issues that I am aware of. Your best bet is to stop all
agents, upgrade the distributor, then the publisher and then the
subscribers.
It is critical to upgrade the distributor and the publisher simultaneously.
The subscribers can wait.
2. You may need to restore your publication database on your subscriber and
then fix it up (ie NFR on all triggers, constraints, and identity columns).
Then do a nosync subscription and do a validation and try to sync any
discrepancies manually.
"Combfilter" <adsf@.asdf.com> wrote in message
news:MPG.1bf96d8fc0db9a09896dc@.news.newsreader.com ...
> 1. I need to upgrade to sp3a on a distributor
> that has about 40 publications to various
> subscribers. I will be going from sql2k rtm to
> sql2k sp3a. Are there any issues as far as
> replication goes patching from rtm to sp3a? I
> cannot afford to reinitilize any of these
> publications.
> 2. Is there like a file size limit on using the
> compress feature of a snapshot? I was able to
> compress a 1gb table fine, but when I tried a
> 10gb one it always fails with a time out.
> tia
> -comb
> btw, Hilary I just ordered your book for
> 45bucks.. hope it helps.
>
|||In article <eEcwkWfxEHA.748
@.TK2MSFTNGP14.phx.gbl>, hilary.cotter@.gmail.com
says...
Actually everyone is already at sp3a except the
dist. Pub and Sub are already sp3a. So I am
just going to do the distributor. I think that
should go on without a hitch right? I shouldn't
have to do anything to any of the db's on the
servers (pub/sub) that are already sp3a.
Do you have any websites or documentation that
explains how to do step 2. in a step by step
format?
Thanks for the info.

> 1. There are not issues that I am aware of. Your best bet is to stop all
> agents, upgrade the distributor, then the publisher and then the
> subscribers.
> It is critical to upgrade the distributor and the publisher simultaneously.
> The subscribers can wait.
> 2. You may need to restore your publication database on your subscriber and
> then fix it up (ie NFR on all triggers, constraints, and identity columns).
> Then do a nosync subscription and do a validation and try to sync any
> discrepancies manually.
>
> "Combfilter" <adsf@.asdf.com> wrote in message
> news:MPG.1bf96d8fc0db9a09896dc@.news.newsreader.com ...
>
>