How is DMO tricked into working with 6.5 during upgrade to 2000

Have a SQL 6.5 DB that we need to upgrade to 2005, which means we have to
upgrade to 2000 first. Doing a two computer upgrade via named pipes.
Finally got the 2000 upgrade wizard up and running, but I hit a roadblock
with the automatic "updating" of DMO on the 6.5 server. The wizard says it
completed the “preparing the SQL_DMO upgrade”, then it goes a few more s
teps
and stops during the “Export Database Objects” step, saying that the sou
rce
DB needs to be upgrade to 7.0 to be administrated by this version of
SQL-DMO.
I, of course, can not find any error messages that the upgrade of DMO
failed, so I start searching the web and Microsoft Knowledge Base, find a fe
w
items (8.3 names for path, SA default db being master) that are similar but
don't solve my problem.
I know it been a long time ago for most of you, but does any one know how
the 2000 upgrade wizard "tricks" the 2000 DMO utility to think the 6.5
database is a 7.0 DB? I see in the output file “Preparing SQL-DMO for
upgrade.out” where tables in master are added and modified, but it looks l
ike
some finally step is not being done. Maybe a setting in the master DB like
the version number? Or is some type of flag being created/set in the
registry? I assume I have some sort of permission or setting problem, but I
can not figure out what it is.
Anybody have any good ideas? I really don’t want to have to upgrade this
DB
by hand.
Should I try an in-place upgrade instead (set up 6.5 on new server, copy DB
over, then do inplace upgrade)? Think I would have any better luck?Hi Robert
Is your SQL 6.5 instance on service pack 5a? If you look at the
compatibility section of SQL 2000 Books online, you will see that there are
quite a few differences between the two versions. You may want to try
installing a SQL 2000 instance on a different machine and then scripting the
database instead. Once you have the database structure you would then use th
e
import/export wizard or BCP to transfer the data. If you did use this method
it would actually be possible to skip SQL 2000!!
Once transferred and thoroughly tested on this instance you could use the
same approach to move to a live situation on the existing server.
John
"RobertCoop" wrote:

> Have a SQL 6.5 DB that we need to upgrade to 2005, which means we have to
> upgrade to 2000 first. Doing a two computer upgrade via named pipes.
> Finally got the 2000 upgrade wizard up and running, but I hit a roadblock
> with the automatic "updating" of DMO on the 6.5 server. The wizard says it
> completed the “preparing the SQL_DMO upgrade”, then it goes a few more
steps
> and stops during the “Export Database Objects” step, saying that the s
ource
> DB needs to be upgrade to 7.0 to be administrated by this version of
> SQL-DMO.
> I, of course, can not find any error messages that the upgrade of DMO
> failed, so I start searching the web and Microsoft Knowledge Base, find a
few
> items (8.3 names for path, SA default db being master) that are similar bu
t
> don't solve my problem.
> I know it been a long time ago for most of you, but does any one know how
> the 2000 upgrade wizard "tricks" the 2000 DMO utility to think the 6.5
> database is a 7.0 DB? I see in the output file “Preparing SQL-DMO for
> upgrade.out” where tables in master are added and modified, but it looks
like
> some finally step is not being done. Maybe a setting in the master DB like
> the version number? Or is some type of flag being created/set in the
> registry? I assume I have some sort of permission or setting problem, but
I
> can not figure out what it is.
> Anybody have any good ideas? I really don’t want to have to upgrade thi
s DB
> by hand.
> Should I try an in-place upgrade instead (set up 6.5 on new server, copy D
B
> over, then do inplace upgrade)? Think I would have any better luck?
>