failed to install sql server express due to Cannot alter the login 'sa'

Hi,

I am using dell precision m60 laptop with xp professional sp2. I had trouble to install sql server due to "Cannot alter the login 'sa'". I am part of administrators for this machine. Below is the log. Any idea? thanks. -dale

SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot alter the login 'sa', because it does not exist or you do not have permission.

Error Code: 0x80073b2f (15151)
Windows Error Text:Source File Name: lib\odbc_statement.h
Compiler Timestamp: Mon Jun 13 14:30:24 2005
Function Name: OdbcStatement::execute_batch@.CnfgSQL@.120
Source Line Number: 91

- Context --

Connecting to SQL Server
ExecuteSqlCommands
USE [master]
<Started SQL statement: Tue Feb 28 15:10:40 2006>declare @.ServerName nvarchar(255) if not exists (select * from sysservers) begin select @.ServerName = Convert(nvarchar(255), SERVERPROPERTY(N'ServerName')) execute sys.sp_addserver @.ServerName, local end
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>ALTER DATABASE model SET RECOVERY SIMPLE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>EXEC sp_configure N'show advanced options', 1 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>DECLARE @.Name AS nvarchar(128), @.LangID AS smallint SELECT @.Name=name, @.LangID=langid FROM syslanguages WHERE lcid=1033 EXEC sp_defaultlanguage N'sa', @.Name EXEC sp_configure N'default language', @.LangID EXEC sp_configure N'default full-text language', 1033 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>EXEC sp_configure N'show advanced options', 0 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>

Looks like if SQL Server 2005 RTM is installed in a Domain where a windows Group named 'sa', 'SA', 'Sa' or 'sA' exists, installation fails when Integrated Security is chosen. However, despite having the Windows group in the Domain, installation with Mixed Security work fine. After having installed successfully with Mixed Secuirty, the server properties can be changed to accept Integrated Security connections only. This should work.|||thanks, Jeff. It is working now.

Failed Assertion

I'm getting the following in the Event log. Has anyone seen this? Any help
is greatly appreciated!
I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
disk array.
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.
Thanks!!
Eric ward
had this problem before try out this kba, not a fix but trace flag 806 gives
better reporting on Disk IO
http://support.microsoft.com/default...b;en-us;841776
"Eric Ward" wrote:

> I'm getting the following in the Event log. Has anyone seen this? Any help
> is greatly appreciated!
> I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> disk array.
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1374
> Failed Assertion = 'm_nVars > 0'.
>
> Thanks!!
> Eric ward
>
|||might need to upgrade the firmwar for your disk controllers to resolve the
problem.
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:41041293-32B2-44A5-AA84-502C335F6681@.microsoft.com...
> had this problem before try out this kba, not a fix but trace flag 806
gives[vbcol=seagreen]
> better reporting on Disk IO
> http://support.microsoft.com/default...b;en-us;841776
> "Eric Ward" wrote:
help[vbcol=seagreen]

Failed Assertion

I'm getting the following in the Event log. Has anyone seen this? Any help
is greatly appreciated!
I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
disk array.
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.
Thanks!!
Eric wardhad this problem before try out this kba, not a fix but trace flag 806 gives
better reporting on Disk IO
http://support.microsoft.com/default.aspx?scid=kb;en-us;841776
"Eric Ward" wrote:
> I'm getting the following in the Event log. Has anyone seen this? Any help
> is greatly appreciated!
> I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> disk array.
> 17066 :
> SQL Server Assertion: File: <recbase.cpp>, line=1374
> Failed Assertion = 'm_nVars > 0'.
>
> Thanks!!
> Eric ward
>|||might need to upgrade the firmwar for your disk controllers to resolve the
problem.
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:41041293-32B2-44A5-AA84-502C335F6681@.microsoft.com...
> had this problem before try out this kba, not a fix but trace flag 806
gives
> better reporting on Disk IO
> http://support.microsoft.com/default.aspx?scid=kb;en-us;841776
> "Eric Ward" wrote:
> > I'm getting the following in the Event log. Has anyone seen this? Any
help
> > is greatly appreciated!
> >
> > I'm running SQL 2000 (Clustered) on Dell PowerEdge 2650 and a PowerVault
> > disk array.
> >
> > 17066 :
> > SQL Server Assertion: File: <recbase.cpp>, line=1374
> > Failed Assertion = 'm_nVars > 0'.
> >
> >
> > Thanks!!
> >
> > Eric ward
> >
> >

extremely bad performance running on huge box ?

hi all !!!
I have a SQL Server 2000 running on a 4 processor 2 GB ram DELL box running
Windows 2003 Server. no other apps run in this machine.
a table witn 20 million records is truncated and recreated once every week.
records are quite simple: (key,value). Table in indexes on key field.
the problem is thar running a "select count(*) from table" takes more than 2
minutes.
even worst, doing a "select * from table where (condition on indexed key
field)" also takes more than 2 minutes.
during these queries, which I do from the Query Analyzer, the overall CPUs
usage is less than 3%.
what could be wrong ? any help would be greatly appreciated.
thanks in advance,
ant.Please post your table DDL (including constraints and indexes), sample data
and problem queries so that we can better help.

> the problem is thar running a "select count(*) from table" takes more than
2
> minutes.
This will require a scan and the duration will be proportional to table
size. If you have only a clustered index and data are not cached, then all
data pages will be read. 2 minutes may or may not be reasonable depending
on your row size and disk configuration.

> even worst, doing a "select * from table where (condition on indexed key
> field)" also takes more than 2 minutes.
This doesn't seem right. If your 'indexed key field' is unique, I would
expect sub-second response. With a non-unique index, I'd expect the
response time to be roughly proportional to the number of rows that satisfy
the condition as long as the expression is sargable.
Hope this helps.
Dan Guzman
SQL Server MVP
"Antonio Lopez Arredondo" <adog@.someplace.com> wrote in message
news:uzLV4A%238DHA.3348@.TK2MSFTNGP09.phx.gbl...
> hi all !!!
> I have a SQL Server 2000 running on a 4 processor 2 GB ram DELL box
running
> Windows 2003 Server. no other apps run in this machine.
> a table witn 20 million records is truncated and recreated once every
week.
> records are quite simple: (key,value). Table in indexes on key field.
> the problem is thar running a "select count(*) from table" takes more than
2
> minutes.
> even worst, doing a "select * from table where (condition on indexed key
> field)" also takes more than 2 minutes.
> during these queries, which I do from the Query Analyzer, the overall CPUs
> usage is less than 3%.
> what could be wrong ? any help would be greatly appreciated.
> thanks in advance,
> ant.
>

extremely bad performance running on huge box ?

hi all !!!
I have a SQL Server 2000 running on a 4 processor 2 GB ram DELL box running
Windows 2003 Server. no other apps run in this machine.
a table witn 20 million records is truncated and recreated once every week.
records are quite simple: (key,value). Table in indexes on key field.
the problem is thar running a "select count(*) from table" takes more than 2
minutes.
even worst, doing a "select * from table where (condition on indexed key
field)" also takes more than 2 minutes.
during these queries, which I do from the Query Analyzer, the overall CPUs
usage is less than 3%.
what could be wrong ? any help would be greatly appreciated.
thanks in advance,
ant.are there 4 physcial processors or is this a Xeon box with
Hyper-Threading,
if HT is enabled, then regardless of the number of actual
processors, try OPTION (MAXDOP 1) or 2
suppose your average row size is 100Bytes, then 20M rows
means the table is 2GB in size
a select count(*) requires a full table scan.
if your data is on a single disk, you can probably achieve
a sequential transfer rate of 50MB/sec, meaning your query
should take 40sec,
if you have 2 disks striped, you ought to be closer to
100MB/sec or 20sec.
if the entire table is in memory, the scan rate should be
800MB/sec,
so something is not right.
on the select *, i need to know the index and the full
query,
also keep in mind the time it QA to receive a large number
of rows
>--Original Message--
>hi all !!!
>I have a SQL Server 2000 running on a 4 processor 2 GB
ram DELL box running
>Windows 2003 Server. no other apps run in this machine.
>a table witn 20 million records is truncated and
recreated once every week.
>records are quite simple: (key,value). Table in indexes
on key field.
>the problem is thar running a "select count(*) from
table" takes more than 2
>minutes.
>even worst, doing a "select * from table where (condition
on indexed key
>field)" also takes more than 2 minutes.
>during these queries, which I do from the Query Analyzer,
the overall CPUs
>usage is less than 3%.
>what could be wrong ? any help would be greatly
appreciated.
>thanks in advance,
> ant.
>
>.
>|||Please post your table DDL (including constraints and indexes), sample data
and problem queries so that we can better help.
> the problem is thar running a "select count(*) from table" takes more than
2
> minutes.
This will require a scan and the duration will be proportional to table
size. If you have only a clustered index and data are not cached, then all
data pages will be read. 2 minutes may or may not be reasonable depending
on your row size and disk configuration.
> even worst, doing a "select * from table where (condition on indexed key
> field)" also takes more than 2 minutes.
This doesn't seem right. If your 'indexed key field' is unique, I would
expect sub-second response. With a non-unique index, I'd expect the
response time to be roughly proportional to the number of rows that satisfy
the condition as long as the expression is sargable.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Antonio Lopez Arredondo" <adog@.someplace.com> wrote in message
news:uzLV4A%238DHA.3348@.TK2MSFTNGP09.phx.gbl...
> hi all !!!
> I have a SQL Server 2000 running on a 4 processor 2 GB ram DELL box
running
> Windows 2003 Server. no other apps run in this machine.
> a table witn 20 million records is truncated and recreated once every
week.
> records are quite simple: (key,value). Table in indexes on key field.
> the problem is thar running a "select count(*) from table" takes more than
2
> minutes.
> even worst, doing a "select * from table where (condition on indexed key
> field)" also takes more than 2 minutes.
> during these queries, which I do from the Query Analyzer, the overall CPUs
> usage is less than 3%.
> what could be wrong ? any help would be greatly appreciated.
> thanks in advance,
> ant.
>