quote:

---

>
>yes. Some of the fixes included in CMS 2002 SP1 also affect stored
>procedures in the CMS repository.
>So you are asked to run DCA at the end of the installation process you
>should do that to allow SP1 to update the CMS repository.
>
>Cheers,
>Stefan

---

quote:

---

> The short version is I want to know if SP1 upgrades/changes any of the
> "Core" Schema for the sql-server database, or wheter it upgrades only

---

quote:

---

> procedures/views/code.---Heres, why.. We are planning to upgrade our live
> site to .NET1.1 and CMS 2002 SP1. The problem is that we have a very

---

quote:

---

> rule that any time we upgrade the live site we have a 'roll back'

---

quote:

---

> Our whole business model (financial research) is delivered via the

---

quote:

---

> and it *must* be up all the time, as well as current. Because we are
> upgrading to .NET1.1 also there is the chance of a problem with

---

quote:

---

> between our code and SP1 or any number of possiblities.We can certainly

---

quote:

---

> a spare copy of the the 'pre SP1' database/website and roll back to that

---

quote:

---

> the case of problems.However, the problem with *that* is that if this
> occured two, three, four days into the week this would create *huge*
> problems as all our content would also 'roll back' in time to the way the
> content was before the upgrade. As I mentioned it is crucial to keep the
> website current. (We accept that in the case of having to rollback there
> would be some down time).So... what to do ? I have a plan, and would like

---

quote:

---

> know if it is totallly daft and/or to hear any recommendations from
> Microsoft (or others).--Here's the plan...Stefan, you say in the below

---

quote:

---

> SP1 updates the stored procedures. Our experiments appear to indicate that
> it updates the Stored Procs but not the actual core table schema.Therefore
> if we set up a 'sql-server replication job' that can copy data (ie just

---

quote:

---

> data in the tables, not the stored procedures) out of the "upgraded SP1"
> database and back to the "roll back, pre-SP1" database, then that would
> provide us with a roll back procedure.Do you think this is a reasonable
> possibility as our rollback process ? If not, what would you

---

quote:

---

> you very much. I am hoping (rudely) for a quick reply as we may need to do
> this soon.Miles>Hi Mark,
>
>
>

---

quote:

---

> The short version is I want to know if SP1 upgrades/changes any of the
> "Core" Schema for the sql-server database, or wheter it upgrades only

---

quote:

---

> procedures/views/code.---Heres, why.. We are planning to upgrade our live
> site to .NET1.1 and CMS 2002 SP1. The problem is that we have a very

---

quote:

---

> rule that any time we upgrade the live site we have a 'roll back'

---

quote:

---

> Our whole business model (financial research) is delivered via the

---

quote:

---

> and it *must* be up all the time, as well as current. Because we are
> upgrading to .NET1.1 also there is the chance of a problem with

---

quote:

---

> between our code and SP1 or any number of possiblities.We can certainly

---

quote:

---

> a spare copy of the the 'pre SP1' database/website and roll back to that

---

quote:

---

> the case of problems.However, the problem with *that* is that if this
> occured two, three, four days into the week this would create *huge*
> problems as all our content would also 'roll back' in time to the way the
> content was before the upgrade. As I mentioned it is crucial to keep the
> website current. (We accept that in the case of having to rollback there
> would be some down time).So... what to do ? I have a plan, and would like

---

quote:

---

> know if it is totallly daft and/or to hear any recommendations from
> Microsoft (or others).--Here's the plan...Stefan, you say in the below

---

quote:

---

> SP1 updates the stored procedures. Our experiments appear to indicate that
> it updates the Stored Procs but not the actual core table schema.Therefore
> if we set up a 'sql-server replication job' that can copy data (ie just

---

quote:

---

> data in the tables, not the stored procedures) out of the "upgraded SP1"
> database and back to the "roll back, pre-SP1" database, then that would
> provide us with a roll back procedure.Do you think this is a reasonable
> possibility as our rollback process ? If not, what would you

---

quote:

---

> you very much. I am hoping (rudely) for a quick reply as we may need to do
> this soon.Miles>Hi Mark,
>
>
>

---

quote:

---

> Hi Mikes,
>
> Stefan could more accurately confirm on this, but I upgraded CMS SP1 with
> the DB, unloaded CMS, Reloaded it on the same CMS DB (the upgraded one ) &
> didnot load SP1. It worked. Now considering that what you are doing should
> be quite a safe bet. Still we probably need to hear it from the horse's
> mouth :-)
>
> Manasvin
>
> "Miles Thompson" < mthompsonBUTWITHOUTANYnastySPAM@creditsi
ghts.NOSPAM.com>
> wrote in message news:%23PW4Bjp5DHA.504@TK2MSFTNGP11.phx.gbl...
> stored
live[QUOTE][color=darkred]
> strict
> strategy.
> website,
> interactions
> keep
> in
the[QUOTE][color=darkred]
like[QUOTE][color=darkred]
> to
> that
that[QUOTE][color=darkred]
schema.Therefore[QUOTE][color=darkred]
> the
> recommend.Thank
do[QUOTE][color=darkred]
>
>

---

quote:

---

> Hi Miles,
>
> although this approach might potentially work, this method would break the
> Microsoft support boundaries.
> Such methods are not supported, sorry.
> The only supported rollback scenario would be to restore the database and
> not parts of it.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no

---

quote:

---

>
>
> "Miles Thompson" < mthompsonBUTWITHOUTANYnastySPAM@creditsi
ghts.NOSPAM.com>
> wrote in message news:#PW4Bjp5DHA.504@TK2MSFTNGP11.phx.gbl...
> stored
live[QUOTE][color=darkred]
> strict
> strategy.
> website,
> interactions
> keep
> in
the[QUOTE][color=darkred]
like[QUOTE][color=darkred]
> to
> that
that[QUOTE][color=darkred]
schema.Therefore[QUOTE][color=darkred]
> the
> recommend.Thank
do[QUOTE][color=darkred]
>
>

---

quote:

---

> That is correct.
> The changes in the database are backward compatible. This means it is
> possible to run an server without SP1 against a SP1 database.
>
> Btw: afaik it is not possible to do the same with a SP1a database. running

---

quote:

---

> server using SP1.
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no

---

quote:

---

>
>
> "Manasvin@msnews.microsoft.com" <manasvin@hotmail.com> wrote in message
> news:O4xx1Nq5DHA.2416@TK2MSFTNGP10.phx.gbl...
with[QUOTE][color=darkred]
&[QUOTE][color=darkred]
should[QUOTE][color=darkred]
< mthompsonBUTWITHOUTANYnastySPAM@creditsi
ghts.NOSPAM.com>[QUOTE][color=darkred]
> live
certainly[QUOTE][color=darkred]
that[QUOTE][color=darkred]
> the
the[QUOTE][color=darkred]
there[QUOTE][color=darkred]
> like
> that
> schema.Therefore
just[QUOTE][color=darkred]
SP1"[QUOTE][color=darkred]
would[QUOTE][color=darkred]
reasonable[QUOTE][color=darkred]
to[QUOTE][color=darkred]
> do
you[QUOTE][color=darkred]
>
>

---

quote:

---

> Thanks for this information.
>
> Does this mean that CMS2002 SP1a is not backwards compatible with CMS2002

---

quote:

---

>
> (Sorry I shoulda been more specific).
>
> Also am I right in thinking that the stored procedures are updated and
> therefore not compatible ? Or is the whole database, including stored

---

quote:

---

> basically compatible/unchanged.
>
> Thanks in advance.
>
>
> Miles
>
> "Stefan [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:enMaJJr5DHA.1968@TK2MSFTNGP11.phx.gbl...
running[QUOTE][color=darkred]
> a
> rights.
> with
one )[QUOTE][color=darkred]
> &
> should
horse's[QUOTE][color=darkred]
> < mthompsonBUTWITHOUTANYnastySPAM@creditsi
ghts.NOSPAM.com>
the[QUOTE][color=darkred]
only[QUOTE][color=darkred]
> certainly
> that
this[QUOTE][color=darkred]
way[QUOTE][color=darkred]
> the
> there
below[QUOTE][color=darkred]
indicate[QUOTE][color=darkred]
> just
> SP1"
> would
> reasonable
> to
> you
>
>

---