Chewing on RAISERROR(N'[Text in brackets]ouch!', 11, 1)

Is this supposed to happen' (MSSQL2K Service pack 3/3a)
/*--
RAISERROR(N'[Presto!][Ho ho!]A minor error occurred.', 10, 1)
RAISERROR(N'[Presto!][Ho ho!]A major error occurred.', 11, 1)
--*/
[Presto!][Ho ho!]A minor error occurred.
Server: Msg 50000, Level 11, State 1, Line 2
A major error occurred.> Is this supposed to happen' (MSSQL2K Service pack 3/3a)
IMHO, no. I would expect the same message text from both statements. The
behavior you observed occurs on my SP4 SQL Server too.
Hope this helps.
Dan Guzman
SQL Server MVP
<rja.carnegie@.excite.com> wrote in message
news:1126615038.811015.292510@.f14g2000cwb.googlegroups.com...
> Is this supposed to happen' (MSSQL2K Service pack 3/3a)
> /*--
> RAISERROR(N'[Presto!][Ho ho!]A minor error occurred.', 10, 1)
> RAISERROR(N'[Presto!][Ho ho!]A major error occurred.', 11, 1)
> --*/
> [Presto!][Ho ho!]A minor error occurred.
> Server: Msg 50000, Level 11, State 1, Line 2
> A major error occurred.
>|||I discussed this with some of the other MVPs and it looks like the culprit
is the Query Analyzer 'parse ODBC message prefixes' option. It looks like
it's too aggressive in removing the ODBC noise from messages.
You'll get the expected results if you turn off the option under
Tools-->Options-->Connections. However, the messages will also be prefixed
with the '[Microsoft][ODBC SQL Server Driver][SQL Server]' stuff.
Hope this helps.
Dan Guzman
SQL Server MVP
<rja.carnegie@.excite.com> wrote in message
news:1126615038.811015.292510@.f14g2000cwb.googlegroups.com...
> Is this supposed to happen' (MSSQL2K Service pack 3/3a)
> /*--
> RAISERROR(N'[Presto!][Ho ho!]A minor error occurred.', 10, 1)
> RAISERROR(N'[Presto!][Ho ho!]A major error occurred.', 11, 1)
> --*/
> [Presto!][Ho ho!]A minor error occurred.
> Server: Msg 50000, Level 11, State 1, Line 2
> A major error occurred.
>|||So long as the missing text isn't piling up somewhere and threatening a
huge problem some time in the future somehow :-)
Thanks to all you MVPs for efforts. So it's Query Analyzer itself
doing it... okay. I noticed it when I did something like,
SET @.workstring =
REPLACE(
N'RAISERROR(''@.{tbl} had some kind of error.'', 16,
1)
, N'@.{tbl}', QUOTENAME(@.tablename))
EXEc sp_executesql @.workstring
(Of course QUOTENAME('TableName') is '[TableName]'.)
Incidentally Google Groups (through which I'm sending this) in its v2
beta version, has a similar issue with article headers - and one group
that I use, alt.fan.pratchett, likes to self-classify articles as [R]
(relevant, on-topic), [I] (off-topic), various others (meta-topical).
These go - even if protected by "Re: ", apparently - but some
experiments with ".[I]", etc, make 'em stay. The issue there isn't
just the Google user's experience but the view that other users get
when a Google user participates.
It seems reasonable that leading text, even a space, will continue to
save my leading parenthetical text here, too.
(And I'll be surprised if Google Groups is held on Microsoft SQL
servers, but I guess why not?)
Does this Query Analyzer issue rate making some kind of official bug
report, I wonder? If telling you doesn't already count... I'd rather
work around it than spend money. I was only being cute with quoted
table names anyway - I don't need to quote my names, but better safe
than sorry and it also helps them to stand out. But in this case, not
;-)
Maybe Microsoft knew already; I find it difficult to pick keywords for
a Knowledge Base search on this issue.
Dan Guzman wrote:
> I discussed this with some of the other MVPs and it looks like the culprit
> is the Query Analyzer 'parse ODBC message prefixes' option. It looks like
> it's too aggressive in removing the ODBC noise from messages.
> You'll get the expected results if you turn off the option under
> Tools-->Options-->Connections. However, the messages will also be prefixe
d
> with the '[Microsoft][ODBC SQL Server Driver][SQL Server]' stuff.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> <rja.carnegie@.excite.com> wrote in message
> news:1126615038.811015.292510@.f14g2000cwb.googlegroups.com...|||> Does this Query Analyzer issue rate making some kind of official bug
> report, I wonder? If telling you doesn't already count... I'd rather
> work around it than spend money.
I agree with your triage assessment. I'd rather see the devs spend their
time tidying up SQL 2005. In any case, I believe the QA behavior should be
documented in a KB article. BTW, it's a non-issue with SQL 2005 since Query
Analyzer is superseded by SQL Server Management Studio.
Hope this helps.
Dan Guzman
SQL Server MVP
<rja.carnegie@.excite.com> wrote in message
news:1126700741.448066.200040@.o13g2000cwo.googlegroups.com...
> So long as the missing text isn't piling up somewhere and threatening a
> huge problem some time in the future somehow :-)
> Thanks to all you MVPs for efforts. So it's Query Analyzer itself
> doing it... okay. I noticed it when I did something like,
> SET @.workstring =
> REPLACE(
> N'RAISERROR(''@.{tbl} had some kind of error.'', 16,
> 1)
> , N'@.{tbl}', QUOTENAME(@.tablename))
> EXEc sp_executesql @.workstring
> (Of course QUOTENAME('TableName') is '[TableName]'.)
> Incidentally Google Groups (through which I'm sending this) in its v2
> beta version, has a similar issue with article headers - and one group
> that I use, alt.fan.pratchett, likes to self-classify articles as [R]
> (relevant, on-topic), [I] (off-topic), various others (meta-topical).
> These go - even if protected by "Re: ", apparently - but some
> experiments with ".[I]", etc, make 'em stay. The issue there isn't
> just the Google user's experience but the view that other users get
> when a Google user participates.
> It seems reasonable that leading text, even a space, will continue to
> save my leading parenthetical text here, too.
> (And I'll be surprised if Google Groups is held on Microsoft SQL
> servers, but I guess why not?)
> Does this Query Analyzer issue rate making some kind of official bug
> report, I wonder? If telling you doesn't already count... I'd rather
> work around it than spend money. I was only being cute with quoted
> table names anyway - I don't need to quote my names, but better safe
> than sorry and it also helps them to stand out. But in this case, not
> ;-)
> Maybe Microsoft knew already; I find it difficult to pick keywords for
> a Knowledge Base search on this issue.
> Dan Guzman wrote:
>|||Dan Guzman wrote:
> I agree with your triage assessment. I'd rather see the devs spend their
> time tidying up SQL 2005.
I don't mind if Bill Gates's money is spent on my bug. Just not my
money, please. ;-)

> In any case, I believe the QA behavior should be
> documented in a KB article.
You think there is one, or someone should make one?

> BTW, it's a non-issue with SQL 2005 since Query
> Analyzer is superseded by SQL Server Management Studio.
A whole new set of quirks, no doubt! But how soon do you think you'll
get us off of 2000'
Thanks again, meanwhile.

CheckSAPwdPolicy Return=''28001''

I need help for the following problem:

We use SQL Server 2005 Express. With a Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) we get the following installation problem.

In the log-file SQLSetup0005_M067RT1107P1_SQL.log we get these lines:

...

Failed to validate sa password error 2704
<EndFunc Name='CheckSAPwdPolicy' Return='28001' GetLastError='0'>
Error Code: 0x80076d61 (28001)
Windows Error Text: Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Fri Feb 9 22:35:05 2007
Function Name: SAPasswordPolicyCheck
Source Line Number: 2727
...

I try it on other PC a Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) - Installation.

Here I got no problems!

What is the reason?

Thank you!

Seems that the first computer has a password policy enabled in Windows which is applied to the sa account (and all appropiate SQL accounts on the server). Either a Local Security Policy or a domain policy is applied to the server which sets the password complexity on the server. If your password is not conform to the complexity rules, the creation of the user will fail. (use the MMC snapin for configuration)

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Thank you very much for your help!

The problem is the local security policy!

Checking the service pack

i am bit confused, when you apply the service pack do you apply it to the
server, to your local(b ecuase you create reports in .net?)You apply it to both, the report server installations and the client (report
designer) installations. It will detect the installed components.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Vanessa" <Vanessa@.discussions.microsoft.com> wrote in message
news:9EBFEBE0-E839-41F3-8E44-63742E3AE928@.microsoft.com...
>i am bit confused, when you apply the service pack do you apply it to the
> server, to your local(b ecuase you create reports in .net?)
>|||i dont quite get how you supposed to apply it to both?
"Robert Bruckner [MSFT]" wrote:
> You apply it to both, the report server installations and the client (report
> designer) installations. It will detect the installed components.
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Vanessa" <Vanessa@.discussions.microsoft.com> wrote in message
> news:9EBFEBE0-E839-41F3-8E44-63742E3AE928@.microsoft.com...
> >i am bit confused, when you apply the service pack do you apply it to the
> > server, to your local(b ecuase you create reports in .net?)
> >
> >
>
>

Check the version of Service pack

How do I check the version of service pack installed to my
sql server...
I tried Select @.@.version
I tried select serverproperty('productlevel')
I get sp3 on the later and now I installed sp3a
still the output of select serverproperty('productlevel')
gives sp3
Please help
Thanks
Alka
Alka,
SERVERPROPERTY is returning SP3 because all the changes in SP3a are setup
related and there are no changes in the database engine.Heres a snippet from
SP3a readme file:
How to Distinguish Between SQL Server 2000 SP3 and SQL Server 2000 SP3a
To determine whether you have SQL Server 2000 SP3 or SQL Server 2000 SP3a
installed, check the version number of the Net-Library file, Ssnetlib.dll.
If the version number of this file is 2000.80.760.0, you have SQL Server
2000 SP3. If the version number of this file is 2000.80.766.0, you have SQL
Server 2000 SP3a.
Assuming that an instance was installed by using the default settings, you
can find the Ssnetlib.dll file in one of these locations:
a.. Default instance: C:\Program Files\Microsoft SQL
Server\Binn\Ssnetlib.dll
b.. Named instance: C:\Program Files\Microsoft
SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka
|||Alka,
The build of SQL did not change from SP3 to SP3A. Check that ssnetlib.dll is
now version 2000.80.766.0 then you have SP3A. If it is 2000.80.760.0 you
have SP3.
Chris Wood
Alberta Department of Energy
CANADA
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka
|||Thanks Dinesh
But my file shows version 2000.80.818.0
Please help...
Thanks
Alka
>--Original Message--
>Alka,
>SERVERPROPERTY is returning SP3 because all the changes
in SP3a are setup
>related and there are no changes in the database
engine.Heres a snippet from
>SP3a readme file:
>How to Distinguish Between SQL Server 2000 SP3 and SQL
Server 2000 SP3a
>To determine whether you have SQL Server 2000 SP3 or SQL
Server 2000 SP3a
>installed, check the version number of the Net-Library
file, Ssnetlib.dll.
>If the version number of this file is 2000.80.760.0, you
have SQL Server
>2000 SP3. If the version number of this file is
2000.80.766.0, you have SQL
>Server 2000 SP3a.
>Assuming that an instance was installed by using the
default settings, you
>can find the Ssnetlib.dll file in one of these locations:
> a.. Default instance: C:\Program Files\Microsoft SQL
>Server\Binn\Ssnetlib.dll
> b.. Named instance: C:\Program Files\Microsoft
>SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dl l
>
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Alka Srivaastava" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
my[vbcol=seagreen]
('productlevel')
>
>.
>
|||Alka,
May be some hotfix(http://support.microsoft.com/?kbid=821688). Can you check
the registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Hotfixes\ ?If its a
hotfix, an entry will be made at this key.BTW, what is the output of select
@.@.version?
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1a5a401c42325$926b1570$a601280a@.phx.gbl...[vbcol=seagreen]
> Thanks Dinesh
> But my file shows version 2000.80.818.0
> Please help...
> Thanks
> Alka
> in SP3a are setup
> engine.Heres a snippet from
> Server 2000 SP3a
> Server 2000 SP3a
> file, Ssnetlib.dll.
> have SQL Server
> 2000.80.766.0, you have SQL
> default settings, you
> wrote in message
> my
> ('productlevel')

Check the version of Service pack

How do I check the version of service pack installed to my
sql server...
I tried Select @.@.version
I tried select serverproperty('productlevel')
I get sp3 on the later and now I installed sp3a
still the output of select serverproperty('productlevel')
gives sp3
Please help
Thanks
AlkaAlka,
SERVERPROPERTY is returning SP3 because all the changes in SP3a are setup
related and there are no changes in the database engine.Heres a snippet from
SP3a readme file:
How to Distinguish Between SQL Server 2000 SP3 and SQL Server 2000 SP3a
To determine whether you have SQL Server 2000 SP3 or SQL Server 2000 SP3a
installed, check the version number of the Net-Library file, Ssnetlib.dll.
If the version number of this file is 2000.80.760.0, you have SQL Server
2000 SP3. If the version number of this file is 2000.80.766.0, you have SQL
Server 2000 SP3a.
Assuming that an instance was installed by using the default settings, you
can find the Ssnetlib.dll file in one of these locations:
a.. Default instance: C:\Program Files\Microsoft SQL
Server\Binn\Ssnetlib.dll
b.. Named instance: C:\Program Files\Microsoft
SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx
.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka|||Alka,
The build of SQL did not change from SP3 to SP3A. Check that ssnetlib.dll is
now version 2000.80.766.0 then you have SP3A. If it is 2000.80.760.0 you
have SP3.
Chris Wood
Alberta Department of Energy
CANADA
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx
.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka|||Thanks Dinesh
But my file shows version 2000.80.818.0
Please help...
Thanks
Alka
>--Original Message--
>Alka,
>SERVERPROPERTY is returning SP3 because all the changes
in SP3a are setup
>related and there are no changes in the database
engine.Heres a snippet from
>SP3a readme file:
>How to Distinguish Between SQL Server 2000 SP3 and SQL
Server 2000 SP3a
>To determine whether you have SQL Server 2000 SP3 or SQL
Server 2000 SP3a
>installed, check the version number of the Net-Library
file, Ssnetlib.dll.
>If the version number of this file is 2000.80.760.0, you
have SQL Server
>2000 SP3. If the version number of this file is
2000.80.766.0, you have SQL
>Server 2000 SP3a.
>Assuming that an instance was installed by using the
default settings, you
>can find the Ssnetlib.dll file in one of these locations:
> a.. Default instance: C:\Program Files\Microsoft SQL
>Server\Binn\Ssnetlib.dll
> b.. Named instance: C:\Program Files\Microsoft
>SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
>
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Alka Srivaastava" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1d1f101c42320$fec140a0$a301280a@.phx
.gbl...
my[vbcol=seagreen]
('productlevel')[vbcol=seagreen]
>
>.
>|||Alka,
May be some hotfix(http://support.microsoft.com/?kbid=821688). Can you check
the registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\Hotfixes\ ?If its a
hotfix, an entry will be made at this key.BTW, what is the output of select
@.@.version?
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1a5a401c42325$926b1570$a601280a@.phx
.gbl...[vbcol=seagreen]
> Thanks Dinesh
> But my file shows version 2000.80.818.0
> Please help...
> Thanks
> Alka
> in SP3a are setup
> engine.Heres a snippet from
> Server 2000 SP3a
> Server 2000 SP3a
> file, Ssnetlib.dll.
> have SQL Server
> 2000.80.766.0, you have SQL
> default settings, you
> wrote in message
> my
> ('productlevel')

Check the version of Service pack

How do I check the version of service pack installed to my
sql server...
I tried Select @.@.version
I tried select serverproperty('productlevel')
I get sp3 on the later and now I installed sp3a
still the output of select serverproperty('productlevel')
gives sp3
Please help
Thanks
AlkaAlka,
SERVERPROPERTY is returning SP3 because all the changes in SP3a are setup
related and there are no changes in the database engine.Heres a snippet from
SP3a readme file:
How to Distinguish Between SQL Server 2000 SP3 and SQL Server 2000 SP3a
To determine whether you have SQL Server 2000 SP3 or SQL Server 2000 SP3a
installed, check the version number of the Net-Library file, Ssnetlib.dll.
If the version number of this file is 2000.80.760.0, you have SQL Server
2000 SP3. If the version number of this file is 2000.80.766.0, you have SQL
Server 2000 SP3a.
Assuming that an instance was installed by using the default settings, you
can find the Ssnetlib.dll file in one of these locations:
a.. Default instance: C:\Program Files\Microsoft SQL
Server\Binn\Ssnetlib.dll
b.. Named instance: C:\Program Files\Microsoft
SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka|||Alka,
The build of SQL did not change from SP3 to SP3A. Check that ssnetlib.dll is
now version 2000.80.766.0 then you have SP3A. If it is 2000.80.760.0 you
have SP3.
Chris Wood
Alberta Department of Energy
CANADA
"Alka Srivaastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
> How do I check the version of service pack installed to my
> sql server...
> I tried Select @.@.version
> I tried select serverproperty('productlevel')
> I get sp3 on the later and now I installed sp3a
> still the output of select serverproperty('productlevel')
> gives sp3
> Please help
> Thanks
> Alka|||Thanks Dinesh
But my file shows version 2000.80.818.0
Please help...
Thanks
Alka
>--Original Message--
>Alka,
>SERVERPROPERTY is returning SP3 because all the changes
in SP3a are setup
>related and there are no changes in the database
engine.Heres a snippet from
>SP3a readme file:
>How to Distinguish Between SQL Server 2000 SP3 and SQL
Server 2000 SP3a
>To determine whether you have SQL Server 2000 SP3 or SQL
Server 2000 SP3a
>installed, check the version number of the Net-Library
file, Ssnetlib.dll.
>If the version number of this file is 2000.80.760.0, you
have SQL Server
>2000 SP3. If the version number of this file is
2000.80.766.0, you have SQL
>Server 2000 SP3a.
>Assuming that an instance was installed by using the
default settings, you
>can find the Ssnetlib.dll file in one of these locations:
> a.. Default instance: C:\Program Files\Microsoft SQL
>Server\Binn\Ssnetlib.dll
> b.. Named instance: C:\Program Files\Microsoft
>SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
>
>--
>Dinesh
>SQL Server MVP
>--
>--
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Alka Srivaastava" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
>> How do I check the version of service pack installed to
my
>> sql server...
>> I tried Select @.@.version
>> I tried select serverproperty('productlevel')
>> I get sp3 on the later and now I installed sp3a
>> still the output of select serverproperty
('productlevel')
>> gives sp3
>> Please help
>> Thanks
>> Alka
>
>.
>|||Alka,
May be some hotfix(http://support.microsoft.com/?kbid=821688). Can you check
the registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Hotfixes\ ?If its a
hotfix, an entry will be made at this key.BTW, what is the output of select
@.@.version?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Alka Srivastava" <anonymous@.discussions.microsoft.com> wrote in message
news:1a5a401c42325$926b1570$a601280a@.phx.gbl...
> Thanks Dinesh
> But my file shows version 2000.80.818.0
> Please help...
> Thanks
> Alka
> >--Original Message--
> >Alka,
> >
> >SERVERPROPERTY is returning SP3 because all the changes
> in SP3a are setup
> >related and there are no changes in the database
> engine.Heres a snippet from
> >SP3a readme file:
> >How to Distinguish Between SQL Server 2000 SP3 and SQL
> Server 2000 SP3a
> >
> >To determine whether you have SQL Server 2000 SP3 or SQL
> Server 2000 SP3a
> >installed, check the version number of the Net-Library
> file, Ssnetlib.dll.
> >If the version number of this file is 2000.80.760.0, you
> have SQL Server
> >2000 SP3. If the version number of this file is
> 2000.80.766.0, you have SQL
> >Server 2000 SP3a.
> >
> >Assuming that an instance was installed by using the
> default settings, you
> >can find the Ssnetlib.dll file in one of these locations:
> > a.. Default instance: C:\Program Files\Microsoft SQL
> >Server\Binn\Ssnetlib.dll
> > b.. Named instance: C:\Program Files\Microsoft
> >SQLServer\MSSQL$<InstanceName>\Binn\Ssnetlib.dll
> >
> >
> >--
> >Dinesh
> >SQL Server MVP
> >--
> >--
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"Alka Srivaastava" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:1d1f101c42320$fec140a0$a301280a@.phx.gbl...
> >> How do I check the version of service pack installed to
> my
> >> sql server...
> >>
> >> I tried Select @.@.version
> >> I tried select serverproperty('productlevel')
> >>
> >> I get sp3 on the later and now I installed sp3a
> >> still the output of select serverproperty
> ('productlevel')
> >> gives sp3
> >>
> >> Please help
> >>
> >> Thanks
> >> Alka
> >
> >
> >.
> >