Upgrading from 6.5 to 2005

We will be upgrading from 6.5 to 2005 as soon as possible. (Yes, it's long
overdue, but the money is now in the budget. Yea!)

We learned from Microsoft's "SQL Server 2005 Implementation and
Maintenance - Self-Paced Training Kit" that there is no direct upgrade path
from 6.5 to 2005. They recommend upgrading from 6.5 to 7 or 2000 and then
from 7 or 2000 to 2005.

Right now, we have both 2000 and 2005 evaluation versions installed on a new
Windows 2003 server. The first phase of the project will be to upgrade a
couple of small test databases. There will be no user access to these
databases when they are in 2000. (We want to similate the same upgrade
process that will eventually take place over a weekend.)

The developers will then test our applications to ensure that client PC's
can connect to the SQL 2005 databases. They will make any changes necessary
to applications. During this time, our users will still be operating against
the 6.5 databases.

Once we have confirmed that this upgrade path works and we have overcome any
problems in our applications, we will purchase a license for 2005 Standard.
Over a weekend, we will upgrade our production databases from 6.5 to 2000 to
2005, and make necessary configuration changes to our user PC's, so that we
can just switch our users from 6.5 to 2005. The users will never connect to
the 2000 version databases.

Can we use an Evaluation edition of 2000 to accomplish the upgrade and data
migration? That is, is it feasible? Is it permitted with an evaluation
version?

Considering that we won't have any users accessing the data while it is in
2000, I would hope that using an evaluation copy of 2000 would be OK.

Thanks in advance,
Linda Dudzic


.

Relevant Pages

  • Re: information store location
    ... I don't see any reason to migrate away from SBS unless ... upgrading is perfectly stable before beginning the upgrade. ... Exchange will move everything itself. ... the logs, then the databases, both per the instructions in the KB. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 and file systems, any recommendations
    ... Many years ago when I worked with Sybase, I had to travel to customer to perform a triple upgrade: ... Had the databases been on plain files, the OS upgrade would have been trivial for them. ... since buffering in the file system could cause problems. ...
    (comp.databases.ms-sqlserver)
  • Re: SQL Server 2005 and file systems, any recommendations
    ... I had to travel to customer to perform a triple upgrade: ... Had the databases been on plain files, the OS upgrade would have been ... since buffering in the file system could cause problems. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Upgrading from 6.5 to 2005
    ... We learned from Microsoft's "SQL Server 2005 Implementation and ... Maintenance - Self-Paced Training Kit" that there is no direct upgrade path ... we have both 2000 and 2005 evaluation versions installed on a new ... databases when they are in 2000. ...
    (microsoft.public.sqlserver.setup)
  • 7.0 to 2000 Upgrade
    ... SQL Server upgrades usually ... latest MDAC prior to beginning the SQL Server upgrade. ... databases before you start this. ... get a restore or attach to work. ...
    (microsoft.public.sqlserver.server)