Migrate from Sql Server 2005 to Sql Server 2000

We are moving from 2000 to 2005 .And I have to come up with an escape
route if after a week or two it is decided performance/other issues
are worse.
.SSIS transfer sql server objects does not cut it for some unknown
reason with one error after the other...
Thanks for your time
massaJust detach the database from the SQL 2000 server and then attach it to the
SQL 2005 server.
Do NOT change the database compatibility level until you are certain that
you will not move it back to the SQL 2000 server.
After attaching, update statistics and re-index.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>|||The database will be upgraded to the SQL 2005 on-disk format when attached
to the SQL 2005 instance. Consequently, it can't be attached back to the
SQL 2000 regardless of the database compatibility level.
Hope this helps.
Dan Guzman
SQL Server MVP
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:O$edDtE2GHA.3372@.TK2MSFTNGP04.phx.gbl...
> Just detach the database from the SQL 2000 server and then attach it to
> the SQL 2005 server.
> Do NOT change the database compatibility level until you are certain that
> you will not move it back to the SQL 2000 server.
> After attaching, update statistics and re-index.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Massa Batheli" <mngong@.gmail.com> wrote in message
> news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>|||> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
That's the way to go back to SQL 2000. There should be a way to get more
details about the errors. Are you logging errors in your package?
Hope this helps.
Dan Guzman
SQL Server MVP
"Massa Batheli" <mngong@.gmail.com> wrote in message
news:1158271663.636547.75900@.b28g2000cwb.googlegroups.com...
>
> We are moving from 2000 to 2005 .And I have to come up with an escape
> route if after a week or two it is decided performance/other issues
> are worse.
> .SSIS transfer sql server objects does not cut it for some unknown
> reason with one error after the other...
>
> Thanks for your time
> massa
>