REPOST - Moving from 7.0 to 2000

Dear All,
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
A
Hi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:

> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>
|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks

>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy[vbcol=seagreen]
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
in[vbcol=seagreen]
like[vbcol=seagreen]
but[vbcol=seagreen]
be
>.
>