 |
|
|
|
Next: Non key granularity attribute in Parent- Child Di..
|
| Author |
Message |
External
Since: May 15, 2006
Posts: 3
|
(Msg. 1) Posted: Thu May 18, 2006 2:55 am
Post subject: Problem upgrading named instance in SQL 2000
Archived from groups: microsoft>public>sqlserver>clients (more info?)
|
|
|
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 |
|
| Back to top |
|
 | |
External
Since: May 14, 2006
Posts: 4
|
(Msg. 2) Posted: Thu May 18, 2006 11:00 am
Post subject: RE: Problem upgrading named instance in SQL 2000 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Are you sure the named instance is also SP3? Double check. Remember, you
have to update each instance seperately.
--
MeanOldDBA
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"sandy" wrote:
> 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
>
> |
|
| Back to top |
|
| |
External
Since: May 15, 2006
Posts: 3
|
(Msg. 3) Posted: Fri May 19, 2006 1:21 am
Post subject: Re: Problem upgrading named instance in SQL 2000 [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hi,
Thanks a lot. That was the problem. I did not apply SP3 to the named
Instance.
Regards,
Sandhya
MeanOldDBA wrote:
> Are you sure the named instance is also SP3? Double check. Remember, you
> have to update each instance seperately.
> --
> MeanOldDBA
>
> http://weblogs.sqlteam.com/derrickl
>
> When life gives you a lemon, fire the DBA.
>
>
> "sandy" wrote:
>
> > 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
> >
> > >> Stay informed about: Problem upgrading named instance in SQL 2000 |
|
| Back to top |
|
| |
| Related Topics: | Named instance connection problem - Have an MSDE named instance which works just fine. Just installed another instance of the same and can only connect to it using OSQL locally, nothing across the network. I made sure to use all the gotcha flags during install to enable network access,..
NT4 client connecting to SQL2000 named instance - I have 1 SQL2000 setup with multiple instances. Have problems connecting ODBC on a NT4 to a named instance. It can connect to the default instance though. Tried both ServerName\instance name, and IP address\instance name. Network connection is fine,..
DEFAULT INSTANCE INSTALLATION PROBLEM ON SQL2005 - I have win2003 machine which is named fenermarket. I have an installed instance which is FENERMARKET\ALISVERISSAATI. I installed sp1 and sp2 too. When i try to install default instance as another instance the setup process give the error.Im sure that...
trying to connect to remote SQL server, get named pipe error - I'm trying to use a asp.net page (aspx) using SqlDataSource to connect to a remote SQL Server 2005. I keep getting the following error: provider: Named Pipes Provider, error: 40 - Could not open a connectio I don't know why my sql client is using named...
Old code not able to connect to unicode instance - Hi, I have a program written in C/C++ compiled with MS Visual Studio 6.0 that fails to connect to a french SQL Server instance (probably a 2005 instance) with "SQL Server does not exist or access denied". I can connect to the instance with ... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
