Hi Folks,

We are now just embarking on our 2k5 upgrade. I have many instances to
upgrade, and all at varying levels. I’m reviewing an upgrade matrix in SQL
Server 2005 unleashed, and I would like confirmation on what I am reading.

Can I upgrade:
SQL 2k SP3/4 Enterprise Edition to SQL 2k5 Standard Edition?
SQL 2k SP3/4 Personal Edition to SQL 2k5 Standard Edition?


If not, I can either go for a side-by-side migration, or downgrade 2k to
Standard edition.

Would appreciate a solid link or 2 to some downgrading documentation.

--
Thanks,

Scott H.

Hi Folks,

Found a posting on page 4, with a good link to upgrade path - at first
glance it seems better than Unleashed.

http://technet.microsoft.com/en-us/l.../ms143393.aspx

However, I would still like your opinion/information on downgrading from 2k
Enterprise Edition in order to migrate to 2k5 SE.
--
Thanks,

Scott H.


"Scott H." wrote:

> Hi Folks,
>
> We are now just embarking on our 2k5 upgrade. I have many instances to
> upgrade, and all at varying levels. I’m reviewing an upgrade matrix in SQL
> Server 2005 unleashed, and I would like confirmation on what I am reading.
>
> Can I upgrade:
> SQL 2k SP3/4 Enterprise Edition to SQL 2k5 Standard Edition?
> SQL 2k SP3/4 Personal Edition to SQL 2k5 Standard Edition?
>
>
> If not, I can either go for a side-by-side migration, or downgrade 2k to
> Standard edition.
>
> Would appreciate a solid link or 2 to some downgrading documentation.
>
> --
> Thanks,
>
> Scott H.

Scott,

I downgraded/upgraded from SQL Server 2000 Enterprise Edition to SQL Server
2005 Standard Edition with no real problems. For me, however, it was not
in-place but a fresh install followed by restoring master, msdb, and
reattaching the user databases from 2000.

The only issues we faced was the feature use. If you are using any
Enterprise Edition features, those will no longer work in Standard Edition.
So, review the relatively few features that are EE only and make sure that
you do not depend on them. (Distributed partitioned views, fully featured
indexed views, log shipping, etc.) Other than that, everything should work
OK.

In SS2000 we had used Enterprise Edition primarily to get more memory
available. However, assuming that you are running on Windows Server 2003 or
higher, SS2005 Standard Edition will use the amount of memory supported by
the operating system. (Truth in experience is, after a few months on 2005 SE
we again upgraded to 2005 EE, so think about your goals.)

If you have not already done so, the SQL Server 2005 Upgrade Advisor is a
free download and well worth your reading the file documentation and
running the check against your existing server.
http://go.microsoft.com/fwlink/?LinkId=45788

The supported upgrade grid of 2000 to 2005 versions is outlined here:
http://msdn2.microsoft.com/en-us/library/ms143393.aspx

RLF


"Scott H." <ScottH@discussions.microsoft.com> wrote in message
news:1E10C700-554D-4D6E-BDA4-D940D2A55BED@microsoft.com...
> Hi Folks,
>
> We are now just embarking on our 2k5 upgrade. I have many instances to
> upgrade, and all at varying levels. I'm reviewing an upgrade matrix in SQL
> Server 2005 unleashed, and I would like confirmation on what I am reading.
>
> Can I upgrade:
> SQL 2k SP3/4 Enterprise Edition to SQL 2k5 Standard Edition?
> SQL 2k SP3/4 Personal Edition to SQL 2k5 Standard Edition?
>
>
> If not, I can either go for a side-by-side migration, or downgrade 2k to
> Standard edition.
>
> Would appreciate a solid link or 2 to some downgrading documentation.
>
> --
> Thanks,
>
> Scott H.

Russell, thanks for your response.

Perhaps I wasn't entirely clear. My question is if I have a 2k EE
installation, can I do an in-place upgrade directly to 2k5 SE without first
downgrading 2k EE to SE? According to the matirx at
http://technet.microsoft.com/en-us/l.../ms143393.aspx I cannot.

I have been playing around with the UA. I have a question or two regarding
this, but will post in another thread.

Thanks again.
--
Thanks,

Scott H.


"Russell Fields" wrote:

>
> Scott,
>
> I downgraded/upgraded from SQL Server 2000 Enterprise Edition to SQL Server
> 2005 Standard Edition with no real problems. For me, however, it was not
> in-place but a fresh install followed by restoring master, msdb, and
> reattaching the user databases from 2000.
>
> The only issues we faced was the feature use. If you are using any
> Enterprise Edition features, those will no longer work in Standard Edition.
> So, review the relatively few features that are EE only and make sure that
> you do not depend on them. (Distributed partitioned views, fully featured
> indexed views, log shipping, etc.) Other than that, everything should work
> OK.
>
> In SS2000 we had used Enterprise Edition primarily to get more memory
> available. However, assuming that you are running on Windows Server 2003 or
> higher, SS2005 Standard Edition will use the amount of memory supported by
> the operating system. (Truth in experience is, after a few months on 2005 SE
> we again upgraded to 2005 EE, so think about your goals.)
>
> If you have not already done so, the SQL Server 2005 Upgrade Advisor is a
> free download and well worth your reading the file documentation and
> running the check against your existing server.
> http://go.microsoft.com/fwlink/?LinkId=45788
>
> The supported upgrade grid of 2000 to 2005 versions is outlined here:
> http://msdn2.microsoft.com/en-us/library/ms143393.aspx
>
> RLF
>
>
> "Scott H." <ScottH@discussions.microsoft.com> wrote in message
> news:1E10C700-554D-4D6E-BDA4-D940D2A55BED@microsoft.com...
> > Hi Folks,
> >
> > We are now just embarking on our 2k5 upgrade. I have many instances to
> > upgrade, and all at varying levels. I'm reviewing an upgrade matrix in SQL
> > Server 2005 unleashed, and I would like confirmation on what I am reading.
> >
> > Can I upgrade:
> > SQL 2k SP3/4 Enterprise Edition to SQL 2k5 Standard Edition?
> > SQL 2k SP3/4 Personal Edition to SQL 2k5 Standard Edition?
> >
> >
> > If not, I can either go for a side-by-side migration, or downgrade 2k to
> > Standard edition.
> >
> > Would appreciate a solid link or 2 to some downgrading documentation.
> >
> > --
> > Thanks,
> >
> > Scott H.
>
>
>