Best way to upgrade

Hi all,
I currently have sql 2000 running under instance name TIMENSQL.
We are setting ourselves to upgrade but obviously need to test etc
etc.
I was thinking of installing 2005 alongside 2000 and migrating db's
across and then testing apps against them. Then one weekend (of
course!) clearing all off 2005 then migrate the lot from 2000 and we
would have fresh data.
I wuld love to then change the instance name to original 2000 name to
fix all issues with ODBC and connection strings etc.
Anyone gone through this senario? Any thoughts
Many thanks
ScottLook in BOL - estimating the size of a table (indexed under "estimating
table size")|||On 14 Jun, 17:00, "Scott Morris" <b...@.bogus.com> wrote:
> Look in BOL - estimating the size of a table (indexed under "estimating
> table size")
that for me Scott'|||> I wuld love to then change the instance name to original 2000 name to
> fix all issues with ODBC and connection strings etc.
Can't change instance name, I'm afraid...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sanpedro" <Scottsanpedro@.gmail.com> wrote in message
news:1181835331.902393.232510@.q19g2000prn.googlegroups.com...
> Hi all,
> I currently have sql 2000 running under instance name TIMENSQL.
> We are setting ourselves to upgrade but obviously need to test etc
> etc.
> I was thinking of installing 2005 alongside 2000 and migrating db's
> across and then testing apps against them. Then one weekend (of
> course!) clearing all off 2005 then migrate the lot from 2000 and we
> would have fresh data.
> I wuld love to then change the instance name to original 2000 name to
> fix all issues with ODBC and connection strings etc.
> Anyone gone through this senario? Any thoughts
> Many thanks
> Scott
>