Problem upgrading named instance in SQL 2000

Hi,

I have installed SQL 2000 Server on my machine with Default Instance
and a named instance viz., Instance1.I tried upgrading

the Database Engine of the Default instance to SQL 2005 Server (using
the 2005 Set up CD). It was upgraded successfully.
I tried upgrading the named instance's Database engien from SQL 2000 to
SQL 2005 server. After selecting the Database Engine

component and clicking Next, I got the following error:


Name: Microsoft SQL Server 2000
Reason: Your upgrade is blocked. For more information about upgrade
support, see the "Version and Edition Upgrades" and

"Hardware and Software Requirements" topics in SQL Server 2005 Setup
Help or SQL Server 2005 Books Online.

Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To
proceed, apply the required service pack and then rerun SQL

Server Setup. For more information about upgrade support, see the
Version and Edition Upgrades topic in SQL Server 2005 Setup

Help or SQL Server 2005 Books Online.


Here are my machine details:
Processor: PIII Processor with
RAM: 512 MB
OS: Windows 2003 Server SP1
SQL2000: Enterprise edition with SP3
sql2005: Enterprise edition

Why is the upgrade not happening with respect to named instance whereas
it si happening with Default instance?

Thanks,
Sandhya

.

Relevant Pages

  • RE: MSDE to SQL Server
    ... I understand that you want to upgrade MSDE instances ... We can upgrade the instance SHAREPOINT to SQL and it is not recommended ... Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: New Hardware, moving
    ... resources to NodeB and repeat the upgrade. ... Senior Database Administrator ... Microsoft SQL Server MVP ... SQL 2000 and Windows 2003 support up to four node clusters. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSSQL on XP-Pro
    ... These old versions of SQL Server should run on XP. ... There are two ways to upgrade. ... upgrade when you run the 7.0 install. ...
    (microsoft.public.sqlserver.setup)
  • Re: upgrading from SQL 7.0 to SQL2000
    ... I like the idea of doing a fresh install of SQL> 2000. ... > 2) install SQL 7.0 on a separate machine which is a test server. ... > 3) Restore the databases from my production server on to my test server> running SQL 7.0. ... While the upgrade should work just fine I like to start>> fresh if possible. ...
    (microsoft.public.sqlserver.setup)
  • Re: A philosophical newbie issue: catch redundant errors via relationships or programmically?
    ... in the GUI front end versus writing a SQL query or otherwise dealing ... if you use Access as a front-end to SQL Server (or some ... other server database engine), then the same applies as with any other tool ...
    (comp.databases.theory)
Loading