May 12, 2010 at 7:32 pm
Hi, we need to migrate our Production server from MSSQL 2000 to MSSQL 2005.
This has to be done on the same server itself. Can anyone advise what is the best way to do this? Thanks in advance for the help.
May 13, 2010 at 9:54 am
I've always been cautious and done side-by-side migrations rather than in-place upgrades, but these should help you:
http://msdn.microsoft.com/en-us/library/cc966519.aspx#EGAA
Greg
May 13, 2010 at 7:32 pm
Thanks for your reply. I have a couple of queries pertaining to side-by-side migration which needs your expertise / help.
1) If we install MSSQL2005 on the same server as MSSQL2000, both instance will have the same database names,e.g. 'ACCOUNT'. In this case, how can we ensure front end application is connecting to 'ACCOUNT' database via ODBC driver in MSSQL2005 instead of MSSQL2000
2) Will this type of installation eats up a lot of disk space and result in slow performance?
Appreciate if you can shed some lights on this area. Many thanks!
May 14, 2010 at 3:24 am
bengchoo.kuah (5/12/2010)
Hi, we need to migrate our Production server from MSSQL 2000 to MSSQL 2005.This has to be done on the same server itself. Can anyone advise what is the best way to do this? Thanks in advance for the help.
First run upgrade advisor on existing instance.
Choose the upgrate option for inplace of upgrade or new .
May 14, 2010 at 9:06 am
bengchoo.kuah (5/13/2010)
Thanks for your reply. I have a couple of queries pertaining to side-by-side migration which needs your expertise / help.1) If we install MSSQL2005 on the same server as MSSQL2000, both instance will have the same database names,e.g. 'ACCOUNT'. In this case, how can we ensure front end application is connecting to 'ACCOUNT' database via ODBC driver in MSSQL2005 instead of MSSQL2000
2) Will this type of installation eats up a lot of disk space and result in slow performance?
Appreciate if you can shed some lights on this area. Many thanks!
1) The SQL 2000 and SQL 2005 instances will have different instance names, which you have to specify in the connection string. So the application can't mistakenly connect to the wrong database.
2) It will use roughly double the disk space that one instance uses. Performance depends on the hardware and whether you have applications use both instances at the same time.
Greg
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply