Hi,
I'm running into an issue with case sensitivity. Here is the setup: I have
SQL Server instance that is CS AS by default. Create new database that is
CI AS. Run a file of SQL against this database to create triggers and get
an error on a variable name in one of the triggers. The variable is
declared as @.szName but used as @.szname. I would have thought that since
this is a trigger on the CI database that it would not matter but the
trigger create must somehow interact with Master or MSDB and since they are
CS this causes a problem? Any options on how to easily make this go away
other than the obvious - changing all triggers (and I would guess stored
procedure code as well). Thanks in advance for any help.
Wayne Antinore> SQL Server instance that is CS AS by default. Create new database that is
> CI AS.
I think you should decide to either (a) use CS only or CI only or (b) use a
different instance for CI. Just wait until you start doing any work that
requires tempdb... you will get collation conflicts all over the place.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Thanks Aaron,
Yikes! Never even got into using tempdb yet. I can only imagine what I
would come across there.
Thanks again,
Wayne
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23rGSiMsBEHA.1380@.TK2MSFTNGP10.phx.gbl...
is
> I think you should decide to either (a) use CS only or CI only or (b) use
a
> different instance for CI. Just wait until you start doing any work that
> requires tempdb... you will get collation conflicts all over the place.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Tuesday, March 27, 2012
Case sensitivity of SQL selects
Hi all
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface )
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> > Hi all,
> >
> > Can anybody tell me how to give a case sensitive select on a non case
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
> >
> > Thanks
> > Roshan
>sql
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface )
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> > Hi all,
> >
> > Can anybody tell me how to give a case sensitive select on a non case
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
> >
> > Thanks
> > Roshan
>sql
Case sensitivity of SQL selects
Hi all,
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface ) ?
Thanks
Roshan
Assuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan
|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>
Can anybody tell me how to give a case sensitive select on a non case sensitive instance of sql server .Is there any setting to be set up ( Which needs to be done programtically not through the interface ) ?
Thanks
Roshan
Assuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan
|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>
Case sensitivity of SQL selects
Hi all,
Can anybody tell me how to give a case sensitive select on a non case sensit
ive instance of sql server .Is there any setting to be set up ( Which needs
to be done programtically not through the interface ) ?
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>
Can anybody tell me how to give a case sensitive select on a non case sensit
ive instance of sql server .Is there any setting to be set up ( Which needs
to be done programtically not through the interface ) ?
Thanks
RoshanAssuming SQL 2000, you can specify a case-sensitive collation for a
case-sensitive query. For example:
USE Northwind
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
You can also add the case-insensitive condition so that indexes can be used
efficiently.
SELECT *
FROM Customers
WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'alfki'
SELECT *
FROM Customers
WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
AND CustomerID = 'ALFKI'
Hope this helps.
Dan Guzman
SQL Server MVP
"Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> Hi all,
> Can anybody tell me how to give a case sensitive select on a non case
sensitive instance of sql server .Is there any setting to be set up ( Which
needs to be done programtically not through the interface ) ?
> Thanks
> Roshan|||In addition Dan's post
This should work on SQL 7 too
create table ABCD
(
courceid smallint not null,
description varchar(20) null
)
insert into ABCD(courceid,description)values (1,'DFh2AcZ')
insert into ABCD(courceid,description)values (2,'dHZ3')
)
SELECT description FROM ABCD where charindex(cast('H' as
varbinary(20)),cast(description as varbinary(20)))> 0
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:u2gDRbBKEHA.3596@.tk2msftngp13.phx.gbl...
> Assuming SQL 2000, you can specify a case-sensitive collation for a
> case-sensitive query. For example:
> USE Northwind
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> You can also add the case-insensitive condition so that indexes can be
used
> efficiently.
> SELECT *
> FROM Customers
> WHERE CustomerID = 'alfki' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'alfki'
> SELECT *
> FROM Customers
> WHERE CustomerID = 'ALFKI' COLLATE SQL_Latin1_General_CP850_BIN
> AND CustomerID = 'ALFKI'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Roshan Jayalath" <anonymous@.discussions.microsoft.com> wrote in message
> news:648CCD5F-2615-4730-B735-3AED0EEEB4CB@.microsoft.com...
> sensitive instance of sql server .Is there any setting to be set up (
Which
> needs to be done programtically not through the interface ) ?
>
Sunday, March 25, 2012
case sensitivity
Is SQL server defaults to case insensitive? I am sure there are ways to
install case sensitive SQL server instance but coming from Sybase
(which is always case sensitive) case insensitivity is something new to
me (it requires coding change etc).
Besides, is there any option I can set to turn on case sensitivity or I
am stuck with it? (I can not reinstall SQL server).
Thanks.Case sensitivity is defined by Collation. Read a bit about collations and
youll see what are your options.
install case sensitive SQL server instance but coming from Sybase
(which is always case sensitive) case insensitivity is something new to
me (it requires coding change etc).
Besides, is there any option I can set to turn on case sensitivity or I
am stuck with it? (I can not reinstall SQL server).
Thanks.Case sensitivity is defined by Collation. Read a bit about collations and
youll see what are your options.
MC
<othellomy@.yahoo.comwrote in message
news:1163396241.216022.146940@.b28g2000cwb.googlegr oups.com...
Quote:
Originally Posted by
Is SQL server defaults to case insensitive? I am sure there are ways to
install case sensitive SQL server instance but coming from Sybase
(which is always case sensitive) case insensitivity is something new to
me (it requires coding change etc).
Besides, is there any option I can set to turn on case sensitivity or I
am stuck with it? (I can not reinstall SQL server).
Thanks.
>
case sensitive instance?
How do I tell if an instance is case sensitive? I know it's something you can set when installing SQL Server but can it be changed after installation?
Run sp_helpsort in query analyzer
"J Jetson" wrote:
> How do I tell if an instance is case sensitive? I know it's something you can set when installing SQL Server but can it be changed after installation?
|||RICHARD SAWTELL
"csb007" <csb007@.discussions.microsoft.com> wrote in message
news:3CEB4190-5DD9-4733-B8BE-A669469D3EE6@.microsoft.com...[vbcol=seagreen]
> Run sp_helpsort in query analyzer
> "J Jetson" wrote:
you can set when installing SQL Server but can it be changed after
installation?
You can change the collation sequence in several different locations.
When you install SQL Server, you pick a default for all databases.
When you issue a CREATE DATABASE, you can specify a different default
sequence, just for that database. When you issue a CREATE TABLE, you can
specify a different sequence for each character datatype in the table.
To change the default server collation sequence essentially requires a
rebuild of the master database.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Have a look in BOL at the topic "collations" - things are now (SQL 2000) a
fair bit more complicated than having a case-sensitive choice only on
installation.
On installation you select the server collation which can be reset by
rebuilding master of reinstallation. This is the one returned by sp_helpsort
or using SERVERPROPERTY('Collation').
There are 2 other levels of collation: database and column, both of which
can be altered directly.
HTH,
Paul Ibison
Run sp_helpsort in query analyzer
"J Jetson" wrote:
> How do I tell if an instance is case sensitive? I know it's something you can set when installing SQL Server but can it be changed after installation?
|||RICHARD SAWTELL
"csb007" <csb007@.discussions.microsoft.com> wrote in message
news:3CEB4190-5DD9-4733-B8BE-A669469D3EE6@.microsoft.com...[vbcol=seagreen]
> Run sp_helpsort in query analyzer
> "J Jetson" wrote:
you can set when installing SQL Server but can it be changed after
installation?
You can change the collation sequence in several different locations.
When you install SQL Server, you pick a default for all databases.
When you issue a CREATE DATABASE, you can specify a different default
sequence, just for that database. When you issue a CREATE TABLE, you can
specify a different sequence for each character datatype in the table.
To change the default server collation sequence essentially requires a
rebuild of the master database.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Have a look in BOL at the topic "collations" - things are now (SQL 2000) a
fair bit more complicated than having a case-sensitive choice only on
installation.
On installation you select the server collation which can be reset by
rebuilding master of reinstallation. This is the one returned by sp_helpsort
or using SERVERPROPERTY('Collation').
There are 2 other levels of collation: database and column, both of which
can be altered directly.
HTH,
Paul Ibison
case sensitive instance?
How do I tell if an instance is case sensitive? I know it's something you ca
n set when installing SQL Server but can it be changed after installation?Run sp_helpsort in query analyzer
"J Jetson" wrote:
> How do I tell if an instance is case sensitive? I know it's something you can set
when installing SQL Server but can it be changed after installation?|||RICHARD SAWTELL
"csb007" <csb007@.discussions.microsoft.com> wrote in message
news:3CEB4190-5DD9-4733-B8BE-A669469D3EE6@.microsoft.com...[vbcol=seagreen]
> Run sp_helpsort in query analyzer
> "J Jetson" wrote:
>
you can set when installing SQL Server but can it be changed after
installation?
You can change the collation sequence in several different locations.
When you install SQL Server, you pick a default for all databases.
When you issue a CREATE DATABASE, you can specify a different default
sequence, just for that database. When you issue a CREATE TABLE, you can
specify a different sequence for each character datatype in the table.
To change the default server collation sequence essentially requires a
rebuild of the master database.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Have a look in BOL at the topic "collations" - things are now (SQL 2000) a
fair bit more complicated than having a case-sensitive choice only on
installation.
On installation you select the server collation which can be reset by
rebuilding master of reinstallation. This is the one returned by sp_helpsort
or using SERVERPROPERTY('Collation').
There are 2 other levels of collation: database and column, both of which
can be altered directly.
HTH,
Paul Ibison
n set when installing SQL Server but can it be changed after installation?Run sp_helpsort in query analyzer
"J Jetson" wrote:
> How do I tell if an instance is case sensitive? I know it's something you can set
when installing SQL Server but can it be changed after installation?|||RICHARD SAWTELL
"csb007" <csb007@.discussions.microsoft.com> wrote in message
news:3CEB4190-5DD9-4733-B8BE-A669469D3EE6@.microsoft.com...[vbcol=seagreen]
> Run sp_helpsort in query analyzer
> "J Jetson" wrote:
>
you can set when installing SQL Server but can it be changed after
installation?
You can change the collation sequence in several different locations.
When you install SQL Server, you pick a default for all databases.
When you issue a CREATE DATABASE, you can specify a different default
sequence, just for that database. When you issue a CREATE TABLE, you can
specify a different sequence for each character datatype in the table.
To change the default server collation sequence essentially requires a
rebuild of the master database.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Have a look in BOL at the topic "collations" - things are now (SQL 2000) a
fair bit more complicated than having a case-sensitive choice only on
installation.
On installation you select the server collation which can be reset by
rebuilding master of reinstallation. This is the one returned by sp_helpsort
or using SERVERPROPERTY('Collation').
There are 2 other levels of collation: database and column, both of which
can be altered directly.
HTH,
Paul Ibison
Thursday, March 22, 2012
Case Sensative Coallation
I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I attach, it remains case sensative. How can I change it to insensative?I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the database changes case sensitivity?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordingly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.
> "Tibor Karaszi" wrote:
> > I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case
sensitivity
> > follows with the database. Can you point to how you determine that the database changes case sensitivity?
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> > news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but
when I
> > attach, it remains case sensative. How can I change it to insensative?
> >
> >
> >
follows with the database. Can you point to how you determine that the database changes case sensitivity?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordingly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.
> "Tibor Karaszi" wrote:
> > I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case
sensitivity
> > follows with the database. Can you point to how you determine that the database changes case sensitivity?
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> > news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but
when I
> > attach, it remains case sensative. How can I change it to insensative?
> >
> >
> >
Case Sensative Coallation
I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I attach, it remains case sensative. How can I change it to insensative?
I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the database changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?
|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordi
ngly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>
|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]
I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the database changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?
|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordi
ngly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>
|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]
Case Sensative Coallation
I have a case-sensative database which I want to attach to an insensative in
stance of SQL Server, but when I attach, it remains case sensative. How can
I change it to insensative?I assume that you mean that you want to attach a SQL Server *database*, not
an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the datab
ase changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance
of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hopi
ng that I could attach a case sensative database to an instance of SQL serve
r which was originally installed with Collation Settings insensative, and ha
ve the database act accordi
ngly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, no
t an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the dat
abase changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing col
lation is not an easy task, search
the archives for more info. If you don't find info there, you can post again
..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping tha
t I could attach a case
sensative database to an instance of SQL server which was originally install
ed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
>
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]sql
stance of SQL Server, but when I attach, it remains case sensative. How can
I change it to insensative?I assume that you mean that you want to attach a SQL Server *database*, not
an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the datab
ase changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance
of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hopi
ng that I could attach a case sensative database to an instance of SQL serve
r which was originally installed with Collation Settings insensative, and ha
ve the database act accordi
ngly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, no
t an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the dat
abase changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing col
lation is not an easy task, search
the archives for more info. If you don't find info there, you can post again
..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping tha
t I could attach a case
sensative database to an instance of SQL server which was originally install
ed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
>
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]sql
Tuesday, March 20, 2012
CASE function
Hi,
I have a date column where the application users puposely enter a date way
in the future as part of their business rule. For instance, entering the yea
r
2033 if the given value for this date column is unknown.
I need to programmatically retrieve this date and represent those
out-of-whack dates to show as the current date + 10 days.
I created the following SELECT stmt. using the CASE function:
SELECT ....
CASE post_datetime
WHEN post_datetime > getdate()+365 THEN getdate()+10
...
However, SQL QA returns an error (Incorrect syntax near '>') when I try to
execute this stmt. What am I doing wrong here. Please help. Thanks.
Regards,
- Rob.Rob wrote:
> Hi,
> I have a date column where the application users puposely enter a date way
> in the future as part of their business rule. For instance, entering the y
ear
> 2033 if the given value for this date column is unknown.
> I need to programmatically retrieve this date and represent those
> out-of-whack dates to show as the current date + 10 days.
> I created the following SELECT stmt. using the CASE function:
> SELECT ....
> CASE post_datetime
> WHEN post_datetime > getdate()+365 THEN getdate()+10
> ...
> However, SQL QA returns an error (Incorrect syntax near '>') when I try to
> execute this stmt. What am I doing wrong here. Please help. Thanks.
> Regards,
> - Rob.
Try this instead:
CASE WHEN post_datetime > GETDATE() + 365 THEN GETDATE() + 10 ELSE
post_datetime END|||> SELECT ....
> CASE post_datetime
> WHEN post_datetime > getdate()+365 THEN getdate()+10
There are two general forms of the CASE expression (it is not a function).
You can either say
CASE [expression] WHEN [value] THEN [value] END
or
CASE WHEN [expression][operator][value] THEN [value] END
You combined the two in a way I don't recall ever seeing (and as you have
found out, the syntax is invalid). You need the latter, because you are
testing a more complex expression than simple equality.
Try:
SELECT
CASE WHEN post_datetime > getdate()+365 THEN getdate()+10 ENDsql
I have a date column where the application users puposely enter a date way
in the future as part of their business rule. For instance, entering the yea
r
2033 if the given value for this date column is unknown.
I need to programmatically retrieve this date and represent those
out-of-whack dates to show as the current date + 10 days.
I created the following SELECT stmt. using the CASE function:
SELECT ....
CASE post_datetime
WHEN post_datetime > getdate()+365 THEN getdate()+10
...
However, SQL QA returns an error (Incorrect syntax near '>') when I try to
execute this stmt. What am I doing wrong here. Please help. Thanks.
Regards,
- Rob.Rob wrote:
> Hi,
> I have a date column where the application users puposely enter a date way
> in the future as part of their business rule. For instance, entering the y
ear
> 2033 if the given value for this date column is unknown.
> I need to programmatically retrieve this date and represent those
> out-of-whack dates to show as the current date + 10 days.
> I created the following SELECT stmt. using the CASE function:
> SELECT ....
> CASE post_datetime
> WHEN post_datetime > getdate()+365 THEN getdate()+10
> ...
> However, SQL QA returns an error (Incorrect syntax near '>') when I try to
> execute this stmt. What am I doing wrong here. Please help. Thanks.
> Regards,
> - Rob.
Try this instead:
CASE WHEN post_datetime > GETDATE() + 365 THEN GETDATE() + 10 ELSE
post_datetime END|||> SELECT ....
> CASE post_datetime
> WHEN post_datetime > getdate()+365 THEN getdate()+10
There are two general forms of the CASE expression (it is not a function).
You can either say
CASE [expression] WHEN [value] THEN [value] END
or
CASE WHEN [expression][operator][value] THEN [value] END
You combined the two in a way I don't recall ever seeing (and as you have
found out, the syntax is invalid). You need the latter, because you are
testing a more complex expression than simple equality.
Try:
SELECT
CASE WHEN post_datetime > getdate()+365 THEN getdate()+10 ENDsql
Thursday, March 8, 2012
Cascade Delete
Is there a way to turn off cascade delete temporarily? Yes, I want to leave
orphan records in this instance. I tried the following:
ALTER TABLE tForm NOCHECK CONSTRAINT
Delete From tformDerek Hart (derekmhart@.yahoo.com) writes:
> Is there a way to turn off cascade delete temporarily? Yes, I want to
> leave orphan records in this instance. I tried the following:
> ALTER TABLE tForm NOCHECK CONSTRAINT
> Delete From tform
You would have to disable the constraints on the referring tables, not
the table you are deleting from.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Why' I see that you name tables with a "t-" prefix, so I am pretty
sure that you do not understada how to design an RDBMS. But that is
only based on 20+ years of education and experience in RDBMS and SQL.
Can you explain this?|||Naming tables with a 't' prefix means I don't know how to design an RDBMS.
Well, my commercial application that I sell for $100,000 that has 110 tables
and 1500 stored procedures sure must be having problems!
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1146871618.195792.312780@.y43g2000cwc.googlegroups.com...
> Why' I see that you name tables with a "t-" prefix, so I am pretty
> sure that you do not understada how to design an RDBMS. But that is
> only based on 20+ years of education and experience in RDBMS and SQL.
> Can you explain this?
>|||Since you want to leavew orphans for some reason, yes, it probalby is
havngh problems -- like orphans! That is what indicates that you don't
know how to design an RDBMS. The leading "t-" and other things are
just symptoms of OO design, ignorance of ISO Standards, etc.
And I have worked for companies in the dor-bomb era that cost muxh more
and were much larger. The reason that the databases were so large was
poor design and lots of orphans -- both tables and rows.|||Orphans are only available for seconds until all the data is filled up in
the database. This conversation is complete.
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1146887407.304043.143670@.u72g2000cwu.googlegroups.com...
> Since you want to leavew orphans for some reason, yes, it probalby is
> havngh problems -- like orphans! That is what indicates that you don't
> know how to design an RDBMS. The leading "t-" and other things are
> just symptoms of OO design, ignorance of ISO Standards, etc.
> And I have worked for companies in the dor-bomb era that cost muxh more
> and were much larger. The reason that the databases were so large was
> poor design and lots of orphans -- both tables and rows.
>|||Derek Hart (derekmhart@.yahoo.com) writes:
> Orphans are only available for seconds until all the data is filled up in
> the database. This conversation is complete.
You mean that for several seconds you commit a breach against the
principles of database design and insult Joe Celko! How dare you?
On a more serious note, when you reapply the constraint, be sure to
use this funny syntax:
ALTER TABLE tbl WITH CHECK CHECK CONSTRAINT fk_xxxx
WITH CHECK instructs SQL Server to actually validate the constraint.
If you leave it out, you get WITH NOCHECK. This is obviously faster,
but there is a price to pay: If the constraint is reenabled WITH
NOCHECK, the constraint is not trusted as far as the optimizer is
concerned. This can lead to poorer execution plans, as the optimizer
can not use the constraint to rule out certain conditions.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I am doing a table update of over 100 tables. I apply this when I begin:
SP_MSFOREACHTABLE 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'
And when I am done I apply
SP_MSFOREACHTABLE 'ALTER TABLE ? CHECK CONSTRAINT ALL'
I believe this properly re-enables the constraints, but does it lead to
poorer execution plans.
And did you mean to have CHECK CHECK CONSTRAINT or just one CHECK?
Derek Hart
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97BBC7AA7F30Yazorman@.127.0.0.1...
> Derek Hart (derekmhart@.yahoo.com) writes:
> You mean that for several seconds you commit a breach against the
> principles of database design and insult Joe Celko! How dare you?
> On a more serious note, when you reapply the constraint, be sure to
> use this funny syntax:
> ALTER TABLE tbl WITH CHECK CHECK CONSTRAINT fk_xxxx
> WITH CHECK instructs SQL Server to actually validate the constraint.
> If you leave it out, you get WITH NOCHECK. This is obviously faster,
> but there is a price to pay: If the constraint is reenabled WITH
> NOCHECK, the constraint is not trusted as far as the optimizer is
> concerned. This can lead to poorer execution plans, as the optimizer
> can not use the constraint to rule out certain conditions.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||IMO it might be easier to insert new parent rows, redirect the child
rows to their new parents, and delete old parents. Also it might be way
faster then re-enabling a constraint on a big table.|||Derek Hart (derekmhart@.yahoo.com) writes:
> I am doing a table update of over 100 tables. I apply this when I begin:
> SP_MSFOREACHTABLE 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'
> And when I am done I apply
> SP_MSFOREACHTABLE 'ALTER TABLE ? CHECK CONSTRAINT ALL'
> I believe this properly re-enables the constraints, but does it lead to
> poorer execution plans.
This reenables the constraint without verifying that existing data
complies with the constraint.
> And did you mean to have CHECK CHECK CONSTRAINT or just one CHECK?
The syntax is indeed
as I wrote. Just check Books Online. :-) Yes, it's really a horrible
syntax.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
orphan records in this instance. I tried the following:
ALTER TABLE tForm NOCHECK CONSTRAINT
Delete From tformDerek Hart (derekmhart@.yahoo.com) writes:
> Is there a way to turn off cascade delete temporarily? Yes, I want to
> leave orphan records in this instance. I tried the following:
> ALTER TABLE tForm NOCHECK CONSTRAINT
> Delete From tform
You would have to disable the constraints on the referring tables, not
the table you are deleting from.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Why' I see that you name tables with a "t-" prefix, so I am pretty
sure that you do not understada how to design an RDBMS. But that is
only based on 20+ years of education and experience in RDBMS and SQL.
Can you explain this?|||Naming tables with a 't' prefix means I don't know how to design an RDBMS.
Well, my commercial application that I sell for $100,000 that has 110 tables
and 1500 stored procedures sure must be having problems!
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1146871618.195792.312780@.y43g2000cwc.googlegroups.com...
> Why' I see that you name tables with a "t-" prefix, so I am pretty
> sure that you do not understada how to design an RDBMS. But that is
> only based on 20+ years of education and experience in RDBMS and SQL.
> Can you explain this?
>|||Since you want to leavew orphans for some reason, yes, it probalby is
havngh problems -- like orphans! That is what indicates that you don't
know how to design an RDBMS. The leading "t-" and other things are
just symptoms of OO design, ignorance of ISO Standards, etc.
And I have worked for companies in the dor-bomb era that cost muxh more
and were much larger. The reason that the databases were so large was
poor design and lots of orphans -- both tables and rows.|||Orphans are only available for seconds until all the data is filled up in
the database. This conversation is complete.
"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1146887407.304043.143670@.u72g2000cwu.googlegroups.com...
> Since you want to leavew orphans for some reason, yes, it probalby is
> havngh problems -- like orphans! That is what indicates that you don't
> know how to design an RDBMS. The leading "t-" and other things are
> just symptoms of OO design, ignorance of ISO Standards, etc.
> And I have worked for companies in the dor-bomb era that cost muxh more
> and were much larger. The reason that the databases were so large was
> poor design and lots of orphans -- both tables and rows.
>|||Derek Hart (derekmhart@.yahoo.com) writes:
> Orphans are only available for seconds until all the data is filled up in
> the database. This conversation is complete.
You mean that for several seconds you commit a breach against the
principles of database design and insult Joe Celko! How dare you?
On a more serious note, when you reapply the constraint, be sure to
use this funny syntax:
ALTER TABLE tbl WITH CHECK CHECK CONSTRAINT fk_xxxx
WITH CHECK instructs SQL Server to actually validate the constraint.
If you leave it out, you get WITH NOCHECK. This is obviously faster,
but there is a price to pay: If the constraint is reenabled WITH
NOCHECK, the constraint is not trusted as far as the optimizer is
concerned. This can lead to poorer execution plans, as the optimizer
can not use the constraint to rule out certain conditions.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||I am doing a table update of over 100 tables. I apply this when I begin:
SP_MSFOREACHTABLE 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'
And when I am done I apply
SP_MSFOREACHTABLE 'ALTER TABLE ? CHECK CONSTRAINT ALL'
I believe this properly re-enables the constraints, but does it lead to
poorer execution plans.
And did you mean to have CHECK CHECK CONSTRAINT or just one CHECK?
Derek Hart
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns97BBC7AA7F30Yazorman@.127.0.0.1...
> Derek Hart (derekmhart@.yahoo.com) writes:
> You mean that for several seconds you commit a breach against the
> principles of database design and insult Joe Celko! How dare you?
> On a more serious note, when you reapply the constraint, be sure to
> use this funny syntax:
> ALTER TABLE tbl WITH CHECK CHECK CONSTRAINT fk_xxxx
> WITH CHECK instructs SQL Server to actually validate the constraint.
> If you leave it out, you get WITH NOCHECK. This is obviously faster,
> but there is a price to pay: If the constraint is reenabled WITH
> NOCHECK, the constraint is not trusted as far as the optimizer is
> concerned. This can lead to poorer execution plans, as the optimizer
> can not use the constraint to rule out certain conditions.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx|||IMO it might be easier to insert new parent rows, redirect the child
rows to their new parents, and delete old parents. Also it might be way
faster then re-enabling a constraint on a big table.|||Derek Hart (derekmhart@.yahoo.com) writes:
> I am doing a table update of over 100 tables. I apply this when I begin:
> SP_MSFOREACHTABLE 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'
> And when I am done I apply
> SP_MSFOREACHTABLE 'ALTER TABLE ? CHECK CONSTRAINT ALL'
> I believe this properly re-enables the constraints, but does it lead to
> poorer execution plans.
This reenables the constraint without verifying that existing data
complies with the constraint.
> And did you mean to have CHECK CHECK CONSTRAINT or just one CHECK?
The syntax is indeed
as I wrote. Just check Books Online. :-) Yes, it's really a horrible
syntax.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Sunday, February 19, 2012
Caption: 'ms_sqlce_se_notification' on reopen application window
Hello,
another problem i couldn't figure out myself:
I have limited my application to one instance. So i call SetForegroundWindow() upon other in InitInstance() of the application when there is already an instance of the same application running.
This works fine most of the time. But sometimes it only shows the title bar(incl. OK-button) of the application with the caption 'ms_sqlce_se_notification'.
Then i have to manually activate it within the list of running programs.
Could it be a notification i don't handle? Or what could be the reason for such a behaviour?
I've already searched the web for it and found almost no resource for this issue. So it would be lovely if someone already solved this problem and could tell me the solution.
Kind regards,
AndreSometimes also 'Default Ime' instead of 'ms_sqlce_se_notification' is displayed as caption on reopening.
So far i have found out that there are often hidden 'system windows' in pda applications on the same level than the main application windows. And that the function FindWindow(..) sometimes find one of the hidden windows first instead of the main applications window. Is that correct?
Greetings,
Andre
|||
Yes you are right. ms_sqlce_se_notification is a hidden system window for use in SQL CE.
Thanks,
Laxmi
|||So, comming back to the original question: How do i by-pass this issue?Regards,
Andre
Caption: 'ms_sqlce_se_notification' on reopen application window
Hello,
another problem i couldn't figure out myself:
I have limited my application to one instance. So i call SetForegroundWindow() upon other in InitInstance() of the application when there is already an instance of the same application running.
This works fine most of the time. But sometimes it only shows the title bar(incl. OK-button) of the application with the caption 'ms_sqlce_se_notification'.
Then i have to manually activate it within the list of running programs.
Could it be a notification i don't handle? Or what could be the reason for such a behaviour?
I've already searched the web for it and found almost no resource for this issue. So it would be lovely if someone already solved this problem and could tell me the solution.
Kind regards,
AndreSometimes also 'Default Ime' instead of 'ms_sqlce_se_notification' is displayed as caption on reopening.
So far i have found out that there are often hidden 'system windows' in pda applications on the same level than the main application windows. And that the function FindWindow(..) sometimes find one of the hidden windows first instead of the main applications window. Is that correct?
Greetings,
Andre
|||
Yes you are right. ms_sqlce_se_notification is a hidden system window for use in SQL CE.
Thanks,
Laxmi
|||So, comming back to the original question: How do i by-pass this issue?Regards,
Andre
Tuesday, February 14, 2012
Can't use SQL Express in VS2005
When I try to add a new database to App_Data in a VS2005sp1 project I get "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user interface".
I have SQL2005sp2 and SQL Express on the system, both services are running, and an instance of the latter called SQLExpress which I can use through SQL Server Management Studio. sp_configure user instances enabled is set to 1. The SQL Server Instance Name in Options | Database Tools | Data Connections is set to SQLExpress ...
I have no idea how to proceed .. any ideas anyone?
Thanks
John
Most causes of this error are solved by deleting the folder where we store the SQL Express User Instance system files, which is C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS. You may need to reboot your computer after this, so just eliminate any concerns and reboot.
The once cause that this will not resolve is if you are working thorugh remote desktop. There is bug in windows that results in the remote login not have certain permissions. The problem is explained in http://support.microsoft.com/Default.aspx?id=896613 and you will need to call Microsoft Support to obtain the Hotfix for the problem.
Hopefully this helps.
Mike
|||Thanks, Mike
That was it. Problem now solved.
John
|||I had the following trouble.- Installed MSSQLEXPRESS
- Installed Visual Studio 2005
- Uninstalled MSSQLEXPRESS
- Installed MSSQLEXPRESS
->the bloody error started appearing.
The suggested method worked perfectly!!
I killed the folder, restarted Studio, now can connect to the databases.
Cheers,
Valekm
Sunday, February 12, 2012
Can't update default instance of SQL 2000 to SP4. Not recognized.
I have a SQL server 2000 server with two instances running. One the
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.comJim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
||||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000
.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212|||The default instance is MSDE (what we nowadays call SQL Server Express). MSD
E had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server s
p. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows N
T 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build
3790: Service Pack 2)
>|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000
.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know an
d
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognize
d.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > ========================================
=============
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > ========================================
=============
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
||||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| ========================================
=============
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ========================================
=============
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > ========================================
=============
| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > ========================================
=============
| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
||||Hello,
I am running into a different issue and I am unable to resolve it. Here
is what happened:
1- I had SQLServer 2000 Client Tools installed on my laptop
2- I installed SQLServer 2005 on the laptop.
3- In order to be able to edit DTS components from SSIS I installed the
DTS Designer Components from the SQL 2005 Feature Pack :
SQLServer2005_DTS.msi
4- Once that is installed, I tried to run SQL Enterprise Manager and now
it can not run. the error message is:
"The procedure entry point ?processExecute@.@.YAXPAUHWND__@.@.PBG1@.Z could
not be located in the dynamic link library SEMSFC.dll"
5- Looking at different website people who encountered this issue
installed SQL2000 Server SP 4 and that fixed it for them.
6- However, when I try to install SP4 I can't figure out how to provide
the instance SA password since I don't believe I have one installed
since this is not the database engine server.
Do you have any suggestions or a solution so that I can run EM again?
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.comJim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
||||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000
.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212|||The default instance is MSDE (what we nowadays call SQL Server Express). MSD
E had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server s
p. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows N
T 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build
3790: Service Pack 2)
>|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000
.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> [url]http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-[/ur
l]
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know an
d
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognize
d.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > ========================================
=============
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > ========================================
=============
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
||||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| ========================================
=============
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ========================================
=============
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/...fc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > ========================================
=============
| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > ========================================
=============
| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
||||Hello,
I am running into a different issue and I am unable to resolve it. Here
is what happened:
1- I had SQLServer 2000 Client Tools installed on my laptop
2- I installed SQLServer 2005 on the laptop.
3- In order to be able to edit DTS components from SSIS I installed the
DTS Designer Components from the SQL 2005 Feature Pack :
SQLServer2005_DTS.msi
4- Once that is installed, I tried to run SQL Enterprise Manager and now
it can not run. the error message is:
"The procedure entry point ?processExecute@.@.YAXPAUHWND__@.@.PBG1@.Z could
not be located in the dynamic link library SEMSFC.dll"
5- Looking at different website people who encountered this issue
installed SQL2000 Server SP 4 and that fixed it for them.
6- However, when I try to install SP4 I can't figure out how to provide
the instance SA password since I don't believe I have one installed
since this is not the database engine server.
Do you have any suggestions or a solution so that I can run EM again?
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Friday, February 10, 2012
Can't update default instance of SQL 2000 to SP4. Not recognized.
I have a SQL server 2000 server with two instances running. One the
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
--
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.comJim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
||||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212|||The default instance is MSDE (what we nowadays call SQL Server Express). MSDE had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server sp. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
>> Jim
>> Can put in here a result of @.@.VERSION from both instances?
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
>|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know and
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > =====================================================| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
||||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > =====================================================| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > =====================================================| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
|
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
--
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.comJim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
||||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212|||The default instance is MSDE (what we nowadays call SQL Server Express). MSDE had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server sp. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
>> Jim
>> Can put in here a result of @.@.VERSION from both instances?
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
>|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know and
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > =====================================================| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > =====================================================| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
||||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| =====================================================| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| =====================================================| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > =====================================================| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > =====================================================| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
|
Can't update default instance of SQL 2000 to SP4. Not recognized.
I have a SQL server 2000 server with two instances running. One the
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.com
Jim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com
|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
|
|||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212
|||The default instance is MSDE (what we nowadays call SQL Server Express). MSDE had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server sp. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
>
|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know and
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>
|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > ================================================== ===
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > ================================================== ===
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
|
|||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| ================================================== ===
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ================================================== ===
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > ================================================== ===
| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > ================================================== ===
| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
|
|||Hello,
I am running into a different issue and I am unable to resolve it. Here
is what happened:
1- I had SQLServer 2000 Client Tools installed on my laptop
2- I installed SQLServer 2005 on the laptop.
3- In order to be able to edit DTS components from SSIS I installed the
DTS Designer Components from the SQL 2005 Feature Pack :
SQLServer2005_DTS.msi
4- Once that is installed, I tried to run SQL Enterprise Manager and now
it can not run. the error message is:
"The procedure entry point ?processExecute@.@.YAXPAUHWND__@.@.PBG1@.Z could
not be located in the dynamic link library SEMSFC.dll"
5- Looking at different website people who encountered this issue
installed SQL2000 Server SP 4 and that fixed it for them.
6- However, when I try to install SP4 I can't figure out how to provide
the instance SA password since I don't believe I have one installed
since this is not the database engine server.
Do you have any suggestions or a solution so that I can run EM again?
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
default, one named.
I tried to upgrade the server to SP4, and I was prompted to choose
which instance to upgrade. I chose the default.
SP4 refused to upgrade the default instance with this message:
"MSSQLSERVER is not a SQL Server 2000 instance."
Stranger, it had no problems upgrading the named instance.
I can't find anything about this in the MSKB and I'm a bit of a babe
in the wood when it comes to SQL Server.
The default instance runs our new accounting server, so 'd sure like
to get it up to date. Thanks for any ideas.
Jim Helfer
Computer Systems Administrator
WTW Architects
Timber Court
127 Andesron St.
Pittsburgh PA 15212
412-321-0551 x330
jhelfer@.wtwarch.com
Jim
Can put in here a result of @.@.VERSION from both instances?
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl...
> I have a SQL server 2000 server with two instances running. One the
> default, one named.
> I tried to upgrade the server to SP4, and I was prompted to choose which
> instance to upgrade. I chose the default.
> SP4 refused to upgrade the default instance with this message:
> "MSSQLSERVER is not a SQL Server 2000 instance."
> Stranger, it had no problems upgrading the named instance.
> I can't find anything about this in the MSKB and I'm a bit of a babe in
> the wood when it comes to SQL Server.
> The default instance runs our new accounting server, so 'd sure like to
> get it up to date. Thanks for any ideas.
>
> --
> Jim Helfer
> Computer Systems Administrator
> WTW Architects
> Timber Court
> 127 Andesron St.
> Pittsburgh PA 15212
> 412-321-0551 x330
> jhelfer@.wtwarch.com
|||Dear Jim,
Thank you for posting here.
From the problem description of the post you submitted, my understanding
is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
default instance, the error message saying "MSSQLSERVER is not a SQL
Server 2000 instance" is received. However, we are able to successfully
apply the Service Pack 4 update onto the named instance. If I have
misunderstood about your concern, feel free to let me know.
Based on the current status, I would like to confirm whether your SQL
Server default instance is installed by MSDE components of SQL Server 2000.
If so, we can conclude that we need the MSDE specific Service Pack 4.
You may use the below link for the download the file
"SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
99a9-b7f0213f8bc5&DisplayLang=en
"
NOTE: To determine whether the version is Desktop Engine, we can use the
command "select @.@.version" to manually check the SQL version.
If the issue still persists, please help me to collect the following log
file to me at v-adamqu@.microsoft.com
%windir%\sqlsp.log
If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help. Thank you for your efforts and time.
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Wed, 27 Jun 2007 19:43:26 -0400
| From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| I have a SQL server 2000 server with two instances running. One the
| default, one named.
|
| I tried to upgrade the server to SP4, and I was prompted to choose
| which instance to upgrade. I chose the default.
|
| SP4 refused to upgrade the default instance with this message:
|
| "MSSQLSERVER is not a SQL Server 2000 instance."
|
| Stranger, it had no problems upgrading the named instance.
|
| I can't find anything about this in the MSKB and I'm a bit of a babe
| in the wood when it comes to SQL Server.
|
| The default instance runs our new accounting server, so 'd sure like
| to get it up to date. Thanks for any ideas.
|
|
| --
| Jim Helfer
| Computer Systems Administrator
| WTW Architects
| Timber Court
| 127 Andesron St.
| Pittsburgh PA 15212
| 412-321-0551 x330
| jhelfer@.wtwarch.com
|
|||Uri Dimant wrote:
> Jim
> Can put in here a result of @.@.VERSION from both instances?
This is the Default instance (which would not install sp4):
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
This is the "WTW1" instance (which would install SP4):
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard
Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
|||Adams Qu [MSFT] wrote:
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
OK, but I don't quite understand what "installed by MSDE components"
means. I did not originally set up the server.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
>
Got it.
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
This is the result:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows
NT 5.2 (Build 3790: Service Pack 2)
So, it does appear that my default instance is "MSDE" (whatever that
means), and I will need to apply the service pack specific for that.
Thank you for your help
JAMES A. HELFER | COMPUTER SYSTEMS ADMINISTRATOR | 412-321-0551 EXT
330 | JHELFER@.WTWARCH.COM | WTW ARCHITECTS | TIMBER COURT |
127 ANDERSON STREET | PITTSBURGH, PA 15212
|||The default instance is MSDE (what we nowadays call SQL Server Express). MSDE had a separate
installer, so you need to service pack it using an MSDE sp, not SQL Server sp. You should be able to
find MSDE service packs at MS similar to finding SQL Server sp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jim Helfer" <JimHelfer@.newsgroup.nospam> wrote in message
news:eOQsHKZuHHA.484@.TK2MSFTNGP06.phx.gbl...
> Uri Dimant wrote:
> This is the Default instance (which would not install sp4):
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.2 (Build 3790:
> Service Pack 2)
>
> This is the "WTW1" instance (which would install SP4):
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c)
> 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
>
|||Adams Qu [MSFT] wrote:
> Dear Jim,
> Thank you for posting here.
>
I obtained the MSDE specific SP, but when I run setup I get "The
Instance Name Specified is Invalid"
Jim Helfer
> From the problem description of the post you submitted, my understanding
> is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
> default instance, the error message saying "MSSQLSERVER is not a SQL
> Server 2000 instance" is received. However, we are able to successfully
> apply the Service Pack 4 update onto the named instance. If I have
> misunderstood about your concern, feel free to let me know.
> Based on the current status, I would like to confirm whether your SQL
> Server default instance is installed by MSDE components of SQL Server 2000.
> If so, we can conclude that we need the MSDE specific Service Pack 4.
> You may use the below link for the download the file
> "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download link:
> Microsoft SQL Server 2000 Service Pack 4
> http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
> 99a9-b7f0213f8bc5&DisplayLang=en
> "
> NOTE: To determine whether the version is Desktop Engine, we can use the
> command "select @.@.version" to manually check the SQL version.
> If the issue still persists, please help me to collect the following log
> file to me at v-adamqu@.microsoft.com
> %windir%\sqlsp.log
> If anything is unclear in my post, please don't hesitate to let me know and
> I will be glad to help. Thank you for your efforts and time.
> Have a nice day!
> Best regards,
> Adams Qu, MCSE, MCDBA, MCTS
> Microsoft Online Support
> Microsoft Global Technical Support Center
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> | Date: Wed, 27 Jun 2007 19:43:26 -0400
> | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
> | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
> | MIME-Version: 1.0
> | Subject: Can't update default instance of SQL 2000 to SP4. Not recognized.
> | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
> | Newsgroups: microsoft.public.sqlserver.server
> | NNTP-Posting-Host: wtwarch.com 66.212.142.243
> | Lines: 1
> | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
> | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
> | X-Tomcat-NG: microsoft.public.sqlserver.server
> |
> | I have a SQL server 2000 server with two instances running. One the
> | default, one named.
> |
> | I tried to upgrade the server to SP4, and I was prompted to choose
> | which instance to upgrade. I chose the default.
> |
> | SP4 refused to upgrade the default instance with this message:
> |
> | "MSSQLSERVER is not a SQL Server 2000 instance."
> |
> | Stranger, it had no problems upgrading the named instance.
> |
> | I can't find anything about this in the MSKB and I'm a bit of a babe
> | in the wood when it comes to SQL Server.
> |
> | The default instance runs our new accounting server, so 'd sure like
> | to get it up to date. Thanks for any ideas.
> |
> |
> | --
> | Jim Helfer
> | Computer Systems Administrator
> | WTW Architects
> | Timber Court
> | 127 Andesron St.
> | Pittsburgh PA 15212
> | 412-321-0551 x330
> | jhelfer@.wtwarch.com
> |
>
|||Dear Jim,
Thank you for your reply.
I understand that we receive the new error "The Instance Name Specified is
Invalid" when attempting to install the specified MSDE Service Pack 4.
Based on my experience, this error usually happens if you double click the
setup package without adding the /upgradesp command line.
Please run your SP4 setup from the command line as follows:
Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\MsdeVerboseLog.txt
If the SP4 package still fails to install, please send the log file
"C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Date: Thu, 28 Jun 2007 17:40:52 -0400
| From: Jim Helfer <jhelfer@.wtwarch.com>
| User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| MIME-Version: 1.0
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| NNTP-Posting-Host: wtwarch.com 66.212.142.243
| Lines: 1
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Adams Qu [MSFT] wrote:
| > Dear Jim,
| >
| > Thank you for posting here.
| >
|
|
|
| I obtained the MSDE specific SP, but when I run setup I get "The
| Instance Name Specified is Invalid"
|
|
| Jim Helfer
|
|
| > From the problem description of the post you submitted, my
understanding
| > is: When attempting to apply the SQL Server 2000 Service Pack 4 to the
| > default instance, the error message saying "MSSQLSERVER is not a SQL
| > Server 2000 instance" is received. However, we are able to successfully
| > apply the Service Pack 4 update onto the named instance. If I have
| > misunderstood about your concern, feel free to let me know.
| >
| > Based on the current status, I would like to confirm whether your SQL
| > Server default instance is installed by MSDE components of SQL Server
2000.
| > If so, we can conclude that we need the MSDE specific Service Pack 4.
| >
| > You may use the below link for the download the file
| > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
link:
| >
| > Microsoft SQL Server 2000 Service Pack 4
| >
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| > 99a9-b7f0213f8bc5&DisplayLang=en
| > "
| > NOTE: To determine whether the version is Desktop Engine, we can use
the
| > command "select @.@.version" to manually check the SQL version.
| >
| > If the issue still persists, please help me to collect the following
log
| > file to me at v-adamqu@.microsoft.com
| >
| > %windir%\sqlsp.log
| >
| > If anything is unclear in my post, please don't hesitate to let me know
and
| > I will be glad to help. Thank you for your efforts and time.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Adams Qu, MCSE, MCDBA, MCTS
| > Microsoft Online Support
| >
| > Microsoft Global Technical Support Center
| >
| > Get Secure! - www.microsoft.com/security
| > ================================================== ===
| > When responding to posts, please "Reply to Group" via your newsreader
so
| > that others may learn and benefit from your issue.
| > ================================================== ===
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --
| > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| > | MIME-Version: 1.0
| > | Subject: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| > | Content-Transfer-Encoding: 7bit
| > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| > | Newsgroups: microsoft.public.sqlserver.server
| > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| > | Lines: 1
| > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| > | X-Tomcat-NG: microsoft.public.sqlserver.server
| > |
| > | I have a SQL server 2000 server with two instances running. One the
| > | default, one named.
| > |
| > | I tried to upgrade the server to SP4, and I was prompted to choose
| > | which instance to upgrade. I chose the default.
| > |
| > | SP4 refused to upgrade the default instance with this message:
| > |
| > | "MSSQLSERVER is not a SQL Server 2000 instance."
| > |
| > | Stranger, it had no problems upgrading the named instance.
| > |
| > | I can't find anything about this in the MSKB and I'm a bit of a
babe
| > | in the wood when it comes to SQL Server.
| > |
| > | The default instance runs our new accounting server, so 'd sure
like
| > | to get it up to date. Thanks for any ideas.
| > |
| > |
| > | --
| > | Jim Helfer
| > | Computer Systems Administrator
| > | WTW Architects
| > | Timber Court
| > | 127 Andesron St.
| > | Pittsburgh PA 15212
| > | 412-321-0551 x330
| > | jhelfer@.wtwarch.com
| > |
| >
|
|||Dear Jim,
How's everything going?
I'm wondering if the suggestion has helped or if you have any further
questions. Please feel free to respond to the newsgroups if you need any
additional help.
Have a nice day!
Best regards,
Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| X-Tomcat-ID: 96360692
| References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
<f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
<eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@.online.microsoft.com (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 29 Jun 2007 07:35:32 GMT
| Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
recognized.
| X-Tomcat-NG: microsoft.public.sqlserver.server
| Message-ID: <bgQnYAiuHHA.3972@.TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.server
| Lines: 153
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19309
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Dear Jim,
|
| Thank you for your reply.
|
| I understand that we receive the new error "The Instance Name Specified
is
| Invalid" when attempting to install the specified MSDE Service Pack 4.
|
| Based on my experience, this error usually happens if you double click
the
| setup package without adding the /upgradesp command line.
|
| Please run your SP4 setup from the command line as follows:
|
| Setup.exe /upgradesp SQLRUN UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
| C:\MsdeVerboseLog.txt
|
| If the SP4 package still fails to install, please send the log file
| "C:\MsdeVerboseLog.txt" to me at v-adamqu@.microsoft.com
|
| Have a nice day!
|
| Best regards,
|
| Adams Qu, MCSE, MCDBA, MCTS
| Microsoft Online Support
|
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
| ================================================== ===
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ================================================== ===
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
| --
| | Date: Thu, 28 Jun 2007 17:40:52 -0400
| | From: Jim Helfer <jhelfer@.wtwarch.com>
| | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | MIME-Version: 1.0
| | Subject: Re: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | References: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | In-Reply-To: <f#50M#UuHHA.360@.TK2MSFTNGHUB02.phx.gbl>
| | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | Content-Transfer-Encoding: 7bit
| | Message-ID: <eH#4A0cuHHA.5036@.TK2MSFTNGP03.phx.gbl>
| | Newsgroups: microsoft.public.sqlserver.server
| | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | Lines: 1
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19298
| | X-Tomcat-NG: microsoft.public.sqlserver.server
| |
| | Adams Qu [MSFT] wrote:
| | > Dear Jim,
| | >
| | > Thank you for posting here.
| | >
| |
| |
| |
| | I obtained the MSDE specific SP, but when I run setup I get "The
| | Instance Name Specified is Invalid"
| |
| |
| | Jim Helfer
| |
| |
| | > From the problem description of the post you submitted, my
| understanding
| | > is: When attempting to apply the SQL Server 2000 Service Pack 4 to
the
| | > default instance, the error message saying "MSSQLSERVER is not a
SQL
| | > Server 2000 instance" is received. However, we are able to
successfully
| | > apply the Service Pack 4 update onto the named instance. If I have
| | > misunderstood about your concern, feel free to let me know.
| | >
| | > Based on the current status, I would like to confirm whether your SQL
| | > Server default instance is installed by MSDE components of SQL Server
| 2000.
| | > If so, we can conclude that we need the MSDE specific Service Pack 4.
| | >
| | > You may use the below link for the download the file
| | > "SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE" from the following download
| link:
| | >
| | > Microsoft SQL Server 2000 Service Pack 4
| | >
|
http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-
| | > 99a9-b7f0213f8bc5&DisplayLang=en
| | > "
| | > NOTE: To determine whether the version is Desktop Engine, we can use
| the
| | > command "select @.@.version" to manually check the SQL version.
| | >
| | > If the issue still persists, please help me to collect the following
| log
| | > file to me at v-adamqu@.microsoft.com
| | >
| | > %windir%\sqlsp.log
| | >
| | > If anything is unclear in my post, please don't hesitate to let me
know
| and
| | > I will be glad to help. Thank you for your efforts and time.
| | >
| | > Have a nice day!
| | >
| | > Best regards,
| | >
| | > Adams Qu, MCSE, MCDBA, MCTS
| | > Microsoft Online Support
| | >
| | > Microsoft Global Technical Support Center
| | >
| | > Get Secure! - www.microsoft.com/security
| | > ================================================== ===
| | > When responding to posts, please "Reply to Group" via your newsreader
| so
| | > that others may learn and benefit from your issue.
| | > ================================================== ===
| | > This posting is provided "AS IS" with no warranties, and confers no
| rights.
| | >
| | > --
| | > | Date: Wed, 27 Jun 2007 19:43:26 -0400
| | > | From: Jim Helfer <JimHelfer@.newsgroup.nospam>
| | > | User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
| | > | MIME-Version: 1.0
| | > | Subject: Can't update default instance of SQL 2000 to SP4. Not
| recognized.
| | > | Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| | > | Content-Transfer-Encoding: 7bit
| | > | Message-ID: <OwVO2TRuHHA.4972@.TK2MSFTNGP05.phx.gbl>
| | > | Newsgroups: microsoft.public.sqlserver.server
| | > | NNTP-Posting-Host: wtwarch.com 66.212.142.243
| | > | Lines: 1
| | > | Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP05.phx.gbl
| | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:19220
| | > | X-Tomcat-NG: microsoft.public.sqlserver.server
| | > |
| | > | I have a SQL server 2000 server with two instances running. One
the
| | > | default, one named.
| | > |
| | > | I tried to upgrade the server to SP4, and I was prompted to
choose
| | > | which instance to upgrade. I chose the default.
| | > |
| | > | SP4 refused to upgrade the default instance with this message:
| | > |
| | > | "MSSQLSERVER is not a SQL Server 2000 instance."
| | > |
| | > | Stranger, it had no problems upgrading the named instance.
| | > |
| | > | I can't find anything about this in the MSKB and I'm a bit of a
| babe
| | > | in the wood when it comes to SQL Server.
| | > |
| | > | The default instance runs our new accounting server, so 'd sure
| like
| | > | to get it up to date. Thanks for any ideas.
| | > |
| | > |
| | > | --
| | > | Jim Helfer
| | > | Computer Systems Administrator
| | > | WTW Architects
| | > | Timber Court
| | > | 127 Andesron St.
| | > | Pittsburgh PA 15212
| | > | 412-321-0551 x330
| | > | jhelfer@.wtwarch.com
| | > |
| | >
| |
|
|
|||Hello,
I am running into a different issue and I am unable to resolve it. Here
is what happened:
1- I had SQLServer 2000 Client Tools installed on my laptop
2- I installed SQLServer 2005 on the laptop.
3- In order to be able to edit DTS components from SSIS I installed the
DTS Designer Components from the SQL 2005 Feature Pack :
SQLServer2005_DTS.msi
4- Once that is installed, I tried to run SQL Enterprise Manager and now
it can not run. the error message is:
"The procedure entry point ?processExecute@.@.YAXPAUHWND__@.@.PBG1@.Z could
not be located in the dynamic link library SEMSFC.dll"
5- Looking at different website people who encountered this issue
installed SQL2000 Server SP 4 and that fixed it for them.
6- However, when I try to install SP4 I can't figure out how to provide
the instance SA password since I don't believe I have one installed
since this is not the database engine server.
Do you have any suggestions or a solution so that I can run EM again?
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Subscribe to:
Posts (Atom)