Transfer DB SQL2005 to SQL2000

[Jutarat]

Hi all
Has anyone moved an Axapta 3 database from SQL 2005 to SQL 2000? Is this
recommended?

Thanks you.

[Luegisdorf]

Hi Jutarat

Are you sure to want to downgrade the DB? I guess you've done a write error.

To move a DB from Server 2000 to Server 2500 works fine, if you leave
running the DB in compatibility mode 2000.

Well, a downgrade could also be possible, but I don't know how to convert a
SQL 2005 DB into a SQL 2000 DB ...

Regards
Patrick

[Lawrence Garvin]

"Luegisdorf" <Luegi...@discussions.microsoft.com> wrote in message
news:01D76465-E361-4CE4...@microsoft.com...

> Hi Jutarat
>
> Are you sure to want to downgrade the DB? I guess you've done a write
> error.
>
> To move a DB from Server 2000 to Server 2500 works fine, if you leave
> running the DB in compatibility mode 2000.
>
> Well, a downgrade could also be possible, but I don't know how to convert
> a
> SQL 2005 DB into a SQL 2000 DB ...

If the database compatibility has not been reset from '8' to '9', then it
may be as simple as backing up/restoring the database, or
detaching/attaching the database, as a compatibility value of '8' means,
strictly speaking, it's still a SQL 2000 database.

Otherwise, probably the likely best methodology for "migrating" a database
from SQL2005 to SQL2000 would be to use the Import/Export wizard to copy the
entire database -- however, I've not done this from SQL2005->SQL2000 either,
so I'm not sure that it can be performed, or even if it runs, that it will
be entirely successful.

Whether it's *recommended* or not, is yet another question... I'll leave
that to an Axapta 3.0 expert to answer (which I am not).

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

[Glibs]

I use the following way.

1. Script all the tables in source DB and run the script at destination DB.
It will create tables with clustered indexes (without all other indexes).

2. Run export DB task (in Management Studio select DB, right click All
tasks\Export DB or something similar). Specify source DB and destination DB.
Select only tables (by default views are transformed into tables in
destination DB).

3. Try to run AOS. It will start with errors. It will lack indexes (not
clustered) in some system tables. Manually script these indexed in source DB
and run script at destination DB. It seemed to me there was about three or
four such indexes.

4. When AOS finally starts run DB synchronization.

I usually use this way to change DB collation.