Looks very hard to me.
Has anyone done a successfull fallback ? And survived the process. The doco
I have found shows it to be a total monster. I appear to have the choice of
no fallback at all;
export/import data (approx 100GB per prod server!);
use a third party utility (approx 100GB per prod server);
setup replication from 2005 back to 2000;
I have proved that you can't restore back from 2005 to 2000, nor can you
detach/attach back to 2000.
There just has to be a fast way to do this.
TIA.Jim
One more is create SSIS Package. Unfortunately I have not played with it
personally
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:0C61339A-ABE5-4C6D-835C-6EAFFC76FF44@.microsoft.com...
> Looks very hard to me.
> Has anyone done a successfull fallback ? And survived the process. The
> doco
> I have found shows it to be a total monster. I appear to have the choice
> of
> no fallback at all;
> export/import data (approx 100GB per prod server!);
> use a third party utility (approx 100GB per prod server);
> setup replication from 2005 back to 2000;
> I have proved that you can't restore back from 2005 to 2000, nor can you
> detach/attach back to 2000.
> There just has to be a fast way to do this.
> TIA.|||Fallback to 2000 is not easy. Think about it, MSFT really does not want you
to turn back. With that said, the best approach is to test your upgrade
plan and test your fallback plan too. Go through the pre and post upgrade
steps just like you are doing it for real. Don't forget to make full use of
tools available at your disposal such as Upgrade Advsior and Upgrade
Assistant (2 different tools - similar names - both are free) so that the
process can be as smooth as possible.
Rick Heiges
SQL Server MVP
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:0C61339A-ABE5-4C6D-835C-6EAFFC76FF44@.microsoft.com...
> Looks very hard to me.
> Has anyone done a successfull fallback ? And survived the process. The
> doco
> I have found shows it to be a total monster. I appear to have the choice
> of
> no fallback at all;
> export/import data (approx 100GB per prod server!);
> use a third party utility (approx 100GB per prod server);
> setup replication from 2005 back to 2000;
> I have proved that you can't restore back from 2005 to 2000, nor can you
> detach/attach back to 2000.
> There just has to be a fast way to do this.
> TIA.|||All true, but someone must have actually done a real fallback ?!
How did you do it, and how painful was it ?
I'm looking at having to fallback with 100GB of application data.
"Rick Heiges" wrote:
> Fallback to 2000 is not easy. Think about it, MSFT really does not want you
> to turn back. With that said, the best approach is to test your upgrade
> plan and test your fallback plan too. Go through the pre and post upgrade
> steps just like you are doing it for real. Don't forget to make full use of
> tools available at your disposal such as Upgrade Advsior and Upgrade
> Assistant (2 different tools - similar names - both are free) so that the
> process can be as smooth as possible.
> Rick Heiges
> SQL Server MVP
> "Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
> news:0C61339A-ABE5-4C6D-835C-6EAFFC76FF44@.microsoft.com...
> > Looks very hard to me.
> >
> > Has anyone done a successfull fallback ? And survived the process. The
> > doco
> > I have found shows it to be a total monster. I appear to have the choice
> > of
> > no fallback at all;
> > export/import data (approx 100GB per prod server!);
> > use a third party utility (approx 100GB per prod server);
> > setup replication from 2005 back to 2000;
> >
> > I have proved that you can't restore back from 2005 to 2000, nor can you
> > detach/attach back to 2000.
> >
> > There just has to be a fast way to do this.
> >
> > TIA.
>
>|||Someone from MS posted the steps needed here awhile back.
But *no* guarantees for success, and it's a bit of work!
You can find them here:
Can I move my SQL Server 2005 database to SQL Server 2000?
http://sql.veranoest.net/sql_faq.htm#move_db_files_from_SQL2005
_to_SQL2000
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SmltIFRyb3dicmlkZ2U=?=<JimTrowbridge@.discussions.microsoft.com> wrote on 25 okt 2007 in
microsoft.public.sqlserver.server:
> All true, but someone must have actually done a real fallback ?!
> How did you do it, and how painful was it ?
> I'm looking at having to fallback with 100GB of application
> data.
> "Rick Heiges" wrote:
>> Fallback to 2000 is not easy. Think about it, MSFT really does
>> not want you to turn back. With that said, the best approach
>> is to test your upgrade plan and test your fallback plan too.
>> Go through the pre and post upgrade steps just like you are
>> doing it for real. Don't forget to make full use of tools
>> available at your disposal such as Upgrade Advsior and Upgrade
>> Assistant (2 different tools - similar names - both are free)
>> so that the process can be as smooth as possible.
>> Rick Heiges
>> SQL Server MVP
>> "Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com>
>> wrote in message
>> news:0C61339A-ABE5-4C6D-835C-6EAFFC76FF44@.microsoft.com...
>> > Looks very hard to me.
>> >
>> > Has anyone done a successfull fallback ? And survived the
>> > process. The doco
>> > I have found shows it to be a total monster. I appear to have
>> > the choice of
>> > no fallback at all;
>> > export/import data (approx 100GB per prod server!);
>> > use a third party utility (approx 100GB per prod server);
>> > setup replication from 2005 back to 2000;
>> >
>> > I have proved that you can't restore back from 2005 to 2000,
>> > nor can you detach/attach back to 2000.
>> >
>> > There just has to be a fast way to do this.
>> >
>> > TIA.|||I did a rollback from Informix 9 to Informix 7 once. While it's a different
engine, the idea is the same.
Basically it was a dump & reload and a MAJOR pain-in-the-ass.
"Jim Trowbridge" <JimTrowbridge@.discussions.microsoft.com> wrote in message
news:0C61339A-ABE5-4C6D-835C-6EAFFC76FF44@.microsoft.com...
> Looks very hard to me.
> Has anyone done a successfull fallback ? And survived the process. The
> doco
> I have found shows it to be a total monster. I appear to have the choice
> of
> no fallback at all;
> export/import data (approx 100GB per prod server!);
> use a third party utility (approx 100GB per prod server);
> setup replication from 2005 back to 2000;
> I have proved that you can't restore back from 2005 to 2000, nor can you
> detach/attach back to 2000.
> There just has to be a fast way to do this.
> TIA.
