Backup on 2005 and restore on 2000

Aloha,
I know this question have been asked before and that it's not possible
to move backups from 2005 to 2000
It's easy to transfer to structure of the database using the scripting
option in SQL 2005, but I have some problems with the data.
I have tried using the export data functionality to move data from 2005
to 2000, but somehow it manages to destroy my identity coloumns.
Instead of moving the identity column values, it restarts the numbering
of them (so it goes e.g. 1,2,3... instead of 23, 40, 42...)
How can I avoid destruction of my identity columns? I have tried to
check the Identity checkbox for each of the tables in the import/export
wizard, but this did not solve my problem
(btw: Is there a way of setting the identify checkbox for all of the
tabels at the same time or do we really need to go into each table?)
Thank you for your help, Mads<Mads.phi@.gmail.com> wrote in message
news:1145620115.151240.274350@.u72g2000cwu.googlegroups.com...
> Aloha,
> I know this question have been asked before and that it's not possible
> to move backups from 2005 to 2000
> It's easy to transfer to structure of the database using the scripting
> option in SQL 2005, but I have some problems with the data.
> I have tried using the export data functionality to move data from 2005
> to 2000, but somehow it manages to destroy my identity coloumns.
> Instead of moving the identity column values, it restarts the numbering
> of them (so it goes e.g. 1,2,3... instead of 23, 40, 42...)
> How can I avoid destruction of my identity columns? I have tried to
> check the Identity checkbox for each of the tables in the import/export
> wizard, but this did not solve my problem
You can try to export the schema and then reset the IDENTITY counter and
then import your data.

> (btw: Is there a way of setting the identify checkbox for all of the
> tabels at the same time or do we really need to go into each table?)
Script it out. (look up the undocumented ms_foreachtable stored proc)
Anywy, this is one of those good arguements for not using Identity columns.

> Thank you for your help, Mads
>