How can I Clear Old Server Names Out Of SQL Server Service
Manager. They are ghosts."Jay Kusch" <Jay.Kusch@.mm-games.com> wrote in message
news:067601c3c578$b3a92520$a001280a@.phx.gbl...
> How can I Clear Old Server Names Out Of SQL Server Service
> Manager. They are ghosts.
You mean the list of servers that display for selection to connect? I do not
believe that you can remove those... If you are talking about something
different, please respond with more detail.
Steve|||This list is kept in the registry
HKEY_CURRENT_USER\Software\Microsoft\MSSQLServer\Client\PrefServers
"Jay Kusch" <Jay.Kusch@.mm-games.com> wrote in message
news:01a601c3c584$82991010$a101280a@.phx.gbl...
> >--Original Message--
> >"Jay Kusch" <Jay.Kusch@.mm-games.com> wrote in message
> >news:067601c3c578$b3a92520$a001280a@.phx.gbl...
> >> How can I Clear Old Server Names Out Of SQL Server
> Service
> >> Manager. They are ghosts.
> >
> >You mean the list of servers that display for selection
> to connect? I do not
> >believe that you can remove those... If you are talking
> about something
> >different, please respond with more detail.
> >
> >Steve
> >
> >
> >
> >
> >.
> >
> Thanks Steve ...
> That was the answer that covers it all. We have had so
> many servers in and out of test and production that my
> server list is just unmanagable. Wish there were some way
> to clear the ghosts. Thanks and Happy Holidays!
> J. Kuschsqlsql
Showing posts with label service. Show all posts
Showing posts with label service. Show all posts
Tuesday, March 27, 2012
Clear Cache sqlrs.ReportingServices2005
I'm using the Reporting Service web service to display my reports to the user.
I've deleted some test reports from the server. I've also gone to the
server, searched the test report names, and deleted those.
When I display the available reports using the Reporting Services web
service, the test reports are still there.
How do I remove Reporting Service reports from the server?
Thanks
--
RandyGo to Report Manager, click on report, properties, delete button.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"randy1200" <randy1200@.newsgroups.nospam> wrote in message
news:F873554A-B145-4800-B93F-65B3F6AFC955@.microsoft.com...
> I'm using the Reporting Service web service to display my reports to the
> user.
> I've deleted some test reports from the server. I've also gone to the
> server, searched the test report names, and deleted those.
> When I display the available reports using the Reporting Services web
> service, the test reports are still there.
> How do I remove Reporting Service reports from the server?
> Thanks
> --
> Randy
I've deleted some test reports from the server. I've also gone to the
server, searched the test report names, and deleted those.
When I display the available reports using the Reporting Services web
service, the test reports are still there.
How do I remove Reporting Service reports from the server?
Thanks
--
RandyGo to Report Manager, click on report, properties, delete button.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"randy1200" <randy1200@.newsgroups.nospam> wrote in message
news:F873554A-B145-4800-B93F-65B3F6AFC955@.microsoft.com...
> I'm using the Reporting Service web service to display my reports to the
> user.
> I've deleted some test reports from the server. I've also gone to the
> server, searched the test report names, and deleted those.
> When I display the available reports using the Reporting Services web
> service, the test reports are still there.
> How do I remove Reporting Service reports from the server?
> Thanks
> --
> Randy
Thursday, March 22, 2012
Clarifications on Queue Service and Queue Readers
Hello,
This is info that I am still not certain about and I just need to make sure, my gut feeling is correct:
This makes perfect sense.
This is info that I am still not certain about and I just need to make sure, my gut feeling is correct:
A.
When a procedure is triggered upon reception of a message in a queue, what happens when the procedure fails and rolls back?
1. Message is left on the Queue.
2. is the worker procedure triggered again for the same message by the queue?
3. I am hoping the Queue keeps on triggering workers until it is empty.
My scenario is that my queue reader procedure only reads one message at a time, thus I do not loop to receive many messages.
B.
For my scenario messages are independent and ordering does not matter.
Thus I want to ensure my Queue reader procedures execute simultaneously. Is reading the Top message in one reader somehow blocking the queue for any other reader procedures? I.e. if I have BEGIN TRANSACTION when reading messages of the Queue, is that effectively going prevent many reader procedures working simultaneously. Again, I want to ensure that Service broker is effectively spawning procedures that work simultaneously.
Thank you very much for the time,
LubomirOnly reading one message per invocation will together slow down you application enough so that the other things you're worried about will probably be minor by comparison. As long as there are enough seperate dialogs so that there's at least one dialog per queue read you should see parallelism because a receive only locks one conversation group. If I understand what you're doing you will have one one dialog per conversation group so you will lock on one dialog per transaction.|||
Hello,
A. Service Broker functionality is entirely driven by the normal transactional operations rules of SQL Server. All effects of any Service Broker verbs (BEGIN DIALOG, SEND, RECEIVE, END CONVERSATION etc) will be undone if the transaction is rolled back. So if a queue reder rollsback a RECEIVE, the messages will be back in the queue, available again for activation. Be careful dough, if you activated stored procedure rollsback frequently, you are in danger of triggering poison message detection mechanism. If the activated procedure rollsback the RECEIVE verb result 5 times in a row, the whole queue will be disabled. For details, see http://msdn2.microsoft.com/en-us/library/ms166137.aspx
And yes, queue readers will continue to be activated as long as there are messages in the queue available for receive. Also, queue readers will be activated each time a database comes online, like at server start up.
B. Queue readers can progress in paralel as long as there are multiple conversations available for processing. RECEIVE verb will lock the conversations on which it returned messages, so that no other queue reader processes messages from the same conversation(s). for more details, see the 'Conversation groups' topic in BOL, at http://msdn2.microsoft.com/en-us/library/ms166131(en-US,SQL.90).aspx
HTH,
~ Remus
This makes perfect sense.
Lubomir
Clarifications on Queue Service and Queue Readers
Hello,
This is info that I am still not certain about and I just need to make sure, my gut feeling is correct:
This makes perfect sense.
This is info that I am still not certain about and I just need to make sure, my gut feeling is correct:
A.
When a procedure is triggered upon reception of a message in a queue, what happens when the procedure fails and rolls back?
1. Message is left on the Queue.
2. is the worker procedure triggered again for the same message by the queue?
3. I am hoping the Queue keeps on triggering workers until it is empty.
My scenario is that my queue reader procedure only reads one message at a time, thus I do not loop to receive many messages.
B.
For my scenario messages are independent and ordering does not matter.
Thus I want to ensure my Queue reader procedures execute simultaneously. Is reading the Top message in one reader somehow blocking the queue for any other reader procedures? I.e. if I have BEGIN TRANSACTION when reading messages of the Queue, is that effectively going prevent many reader procedures working simultaneously. Again, I want to ensure that Service broker is effectively spawning procedures that work simultaneously.
Thank you very much for the time,
LubomirOnly reading one message per invocation will together slow down you application enough so that the other things you're worried about will probably be minor by comparison. As long as there are enough seperate dialogs so that there's at least one dialog per queue read you should see parallelism because a receive only locks one conversation group. If I understand what you're doing you will have one one dialog per conversation group so you will lock on one dialog per transaction.|||
Hello,
A. Service Broker functionality is entirely driven by the normal transactional operations rules of SQL Server. All effects of any Service Broker verbs (BEGIN DIALOG, SEND, RECEIVE, END CONVERSATION etc) will be undone if the transaction is rolled back. So if a queue reder rollsback a RECEIVE, the messages will be back in the queue, available again for activation. Be careful dough, if you activated stored procedure rollsback frequently, you are in danger of triggering poison message detection mechanism. If the activated procedure rollsback the RECEIVE verb result 5 times in a row, the whole queue will be disabled. For details, see http://msdn2.microsoft.com/en-us/library/ms166137.aspx
And yes, queue readers will continue to be activated as long as there are messages in the queue available for receive. Also, queue readers will be activated each time a database comes online, like at server start up.
B. Queue readers can progress in paralel as long as there are multiple conversations available for processing. RECEIVE verb will lock the conversations on which it returned messages, so that no other queue reader processes messages from the same conversation(s). for more details, see the 'Conversation groups' topic in BOL, at http://msdn2.microsoft.com/en-us/library/ms166131(en-US,SQL.90).aspx
HTH,
~ Remus
This makes perfect sense.
Clarification on SQL Server Reporting Services 2005
Are all of the Reporting Services service packs handled in the SQL Server
service packs?
So, no more separate services packs for reporting services like in SQL
Server Reporting Services 2000.
Thanks
ReevesSo far it is. I haven't heard anything about that changing.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Reeves Smith" <ReevesSmith@.discussions.microsoft.com> wrote in message
news:B1BFE079-0E58-4FB0-BC06-932C4B072C19@.microsoft.com...
> Are all of the Reporting Services service packs handled in the SQL Server
> service packs?
> So, no more separate services packs for reporting services like in SQL
> Server Reporting Services 2000.
> Thanks
> Reeves
>
service packs?
So, no more separate services packs for reporting services like in SQL
Server Reporting Services 2000.
Thanks
ReevesSo far it is. I haven't heard anything about that changing.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Reeves Smith" <ReevesSmith@.discussions.microsoft.com> wrote in message
news:B1BFE079-0E58-4FB0-BC06-932C4B072C19@.microsoft.com...
> Are all of the Reporting Services service packs handled in the SQL Server
> service packs?
> So, no more separate services packs for reporting services like in SQL
> Server Reporting Services 2000.
> Thanks
> Reeves
>
Sunday, March 11, 2012
Choose a default hierarchy in a dimension
Hi all,
I explain my case. In a Article dimension I have 3 hierarchies (Natures, Staven, Service). When I browse my cube in bids with this exemple :
on rows axis I drag and drop article dimension
on columns axis I drag and drop a time dimension
on data area I made the same operation with a mesure
Then wen I expand article dimension the hierarchy I saw is Natures. I don't want it. I want Service one. How can i do that?
In advance thanks for your help.
Christophe
The first hierarchy you create in BIDS will be your default hierarchy. IE: The Top/left-most hierarchy you see in BIDS.|||Hi,
Thanks for your reply. It's impossible to change that?
Christophe.
|||Hey,You could recreate your hierarchies (if it's not too much of a pain). Or, I haven't tried this yet but assume it'll work, you could just change the order of your hierarchies in XMLA.
So, just script your dimension to a new query editor, search for your hierarchies, (you're looking for the <Hierarchies></Hierarchies> tags), and move the hierarchy you want to be default to the top of the list.
C
Thursday, March 8, 2012
Chinese characters doesn't print correctly
I develop my report in VS2005 and it print out with the Chinese characters
but when I deployed it to reporting service and print it I get boxes that
replaced the Chinese characters. The Chinese character is held in text boxes
in the report that are not queried from the database. The Chinese characters
are static headers.
--
Thank you,
The DiepHi Diep,
Since you were using a static report without querying from your database,
could you please send your report to me (changliw_at_microsoft_dot_com) for
further research?
Currently I performed a simple test with a TextBox header which was filled
with Chinese characters. After I deploy it to my report server, it worked
fine. The Chinese characters were displayed without any problem.
Look forward to your response. I am very glad to work with you for further
research.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||After I installed the Report Viewer 2005 service pack 1 and reboot my server
the report printed Chinese characters fine. Thank you.
--
Thank you,
The Diep
"Charles Wang[MSFT]" wrote:
> Hi Diep,
> Since you were using a static report without querying from your database,
> could you please send your report to me (changliw_at_microsoft_dot_com) for
> further research?
> Currently I performed a simple test with a TextBox header which was filled
> with Chinese characters. After I deploy it to my report server, it worked
> fine. The Chinese characters were displayed without any problem.
> Look forward to your response. I am very glad to work with you for further
> research.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Hi Diep,
Thank you for your reply and the detailed additional feedback on how you
were successful in resolving this issue. This information has been added to
Microsoft's database. Your solution will benefit many other users, and we
really value having you as a Microsoft customer.
If you have any other questions or concerns, please do not hesitate to
contact us. It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi
I have the same problem: the legend of a chart displays boxes instead of
chinese characters.
I've installed the Report Viewer 2005 service pack 1 on my local pc and it
works fine. But when I've installed the service pack on the server, in the
report the chinese characters are still replaced with boxes! Where is the
problem?
The OS on the pc used for development is Windows 2000 service pack 4; the
server OS is Windows Server 2003 standard edition service pack 1.
Thank you
Renato|||I have it working on my server 2003. I installed the service pack 1 from
here http://support.microsoft.com/kb/933137 then I installed some chinese
true font on my server as well. The chinese characters still didn't display
correctly until I rebooted my system.
--
Thank you,
The Diep
"Renato" wrote:
> Hi
> I have the same problem: the legend of a chart displays boxes instead of
> chinese characters.
> I've installed the Report Viewer 2005 service pack 1 on my local pc and it
> works fine. But when I've installed the service pack on the server, in the
> report the chinese characters are still replaced with boxes! Where is the
> problem?
> The OS on the pc used for development is Windows 2000 service pack 4; the
> server OS is Windows Server 2003 standard edition service pack 1.
> Thank you
> Renato
>|||Hi Renato,
If you are a MSDN Managed Newsgroup user, could you please have a new post
so that we can assist you more dedicatedly?
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@.microsoft.com.
=========================================================This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
but when I deployed it to reporting service and print it I get boxes that
replaced the Chinese characters. The Chinese character is held in text boxes
in the report that are not queried from the database. The Chinese characters
are static headers.
--
Thank you,
The DiepHi Diep,
Since you were using a static report without querying from your database,
could you please send your report to me (changliw_at_microsoft_dot_com) for
further research?
Currently I performed a simple test with a TextBox header which was filled
with Chinese characters. After I deploy it to my report server, it worked
fine. The Chinese characters were displayed without any problem.
Look forward to your response. I am very glad to work with you for further
research.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||After I installed the Report Viewer 2005 service pack 1 and reboot my server
the report printed Chinese characters fine. Thank you.
--
Thank you,
The Diep
"Charles Wang[MSFT]" wrote:
> Hi Diep,
> Since you were using a static report without querying from your database,
> could you please send your report to me (changliw_at_microsoft_dot_com) for
> further research?
> Currently I performed a simple test with a TextBox header which was filled
> with Chinese characters. After I deploy it to my report server, it worked
> fine. The Chinese characters were displayed without any problem.
> Look forward to your response. I am very glad to work with you for further
> research.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Hi Diep,
Thank you for your reply and the detailed additional feedback on how you
were successful in resolving this issue. This information has been added to
Microsoft's database. Your solution will benefit many other users, and we
really value having you as a Microsoft customer.
If you have any other questions or concerns, please do not hesitate to
contact us. It is always our pleasure to be of assistance.
Have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Hi
I have the same problem: the legend of a chart displays boxes instead of
chinese characters.
I've installed the Report Viewer 2005 service pack 1 on my local pc and it
works fine. But when I've installed the service pack on the server, in the
report the chinese characters are still replaced with boxes! Where is the
problem?
The OS on the pc used for development is Windows 2000 service pack 4; the
server OS is Windows Server 2003 standard edition service pack 1.
Thank you
Renato|||I have it working on my server 2003. I installed the service pack 1 from
here http://support.microsoft.com/kb/933137 then I installed some chinese
true font on my server as well. The chinese characters still didn't display
correctly until I rebooted my system.
--
Thank you,
The Diep
"Renato" wrote:
> Hi
> I have the same problem: the legend of a chart displays boxes instead of
> chinese characters.
> I've installed the Report Viewer 2005 service pack 1 on my local pc and it
> works fine. But when I've installed the service pack on the server, in the
> report the chinese characters are still replaced with boxes! Where is the
> problem?
> The OS on the pc used for development is Windows 2000 service pack 4; the
> server OS is Windows Server 2003 standard edition service pack 1.
> Thank you
> Renato
>|||Hi Renato,
If you are a MSDN Managed Newsgroup user, could you please have a new post
so that we can assist you more dedicatedly?
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@.microsoft.com.
=========================================================This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================
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.
/*--
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.
Wednesday, March 7, 2012
Checksum problem on system database
Hey there,
we're having an issue with the SQL (MSDE) database that sharepoint uses.
The service starts and immediately stops. In the logs (in dutch) there's
an error: "Het checksumbestand van de systeemdatabase heeft een
ongeldige ondertekening." freely translated it says "The checksumfile
from the system database has a invalid signature".
Anyone know how to solve this or where start searching? Does SQL have
something like eseutil I might try to repair the database?
TIA
hi,
Freaky wrote:
> Hey there,
> we're having an issue with the SQL (MSDE) database that sharepoint
> uses. The service starts and immediately stops. In the logs (in
> dutch) there's an error: "Het checksumbestand van de systeemdatabase
> heeft een ongeldige ondertekening." freely translated it says "The
> checksumfile from the system database has a invalid signature".
> Anyone know how to solve this or where start searching? Does SQL have
> something like eseutil I might try to repair the database?
if you have a valid master database backup, you can restore it as indicated
in http://msdn2.microsoft.com/en-us/library/Aa173557(SQL.80).aspx and
http://msdn2.microsoft.com/en-us/library/Aa176749(SQL.80).aspx ... if you
don't, you are in trouble, as MSDE does not provide the Rebuild utility
(rebuildm.exe) and the scripts to re-generate it.. if this is the case, you
have to uninstall and reinstall the MSDE instance.. you can or course keep
your user's databases files an re-attach them once re-installed..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Hey Andrea,
thx for the re. I was already afraid I would have to reinstall. It's the
instance from sharepoint. We do maintenance at a lot of customers and
some have full SQL versions so perhaps I could use the rebuildm tool
there. But reinstalling sharepoint and replacing the database STS and
STS_Config might be faster as I think those are the only ones that matter.
Anyways thanks again
Andrea Montanari wrote:
> hi,
> Freaky wrote:
> if you have a valid master database backup, you can restore it as indicated
> in http://msdn2.microsoft.com/en-us/library/Aa173557(SQL.80).aspx and
> http://msdn2.microsoft.com/en-us/library/Aa176749(SQL.80).aspx ... if you
> don't, you are in trouble, as MSDE does not provide the Rebuild utility
> (rebuildm.exe) and the scripts to re-generate it.. if this is the case, you
> have to uninstall and reinstall the MSDE instance.. you can or course keep
> your user's databases files an re-attach them once re-installed..
> regards
we're having an issue with the SQL (MSDE) database that sharepoint uses.
The service starts and immediately stops. In the logs (in dutch) there's
an error: "Het checksumbestand van de systeemdatabase heeft een
ongeldige ondertekening." freely translated it says "The checksumfile
from the system database has a invalid signature".
Anyone know how to solve this or where start searching? Does SQL have
something like eseutil I might try to repair the database?
TIA
hi,
Freaky wrote:
> Hey there,
> we're having an issue with the SQL (MSDE) database that sharepoint
> uses. The service starts and immediately stops. In the logs (in
> dutch) there's an error: "Het checksumbestand van de systeemdatabase
> heeft een ongeldige ondertekening." freely translated it says "The
> checksumfile from the system database has a invalid signature".
> Anyone know how to solve this or where start searching? Does SQL have
> something like eseutil I might try to repair the database?
if you have a valid master database backup, you can restore it as indicated
in http://msdn2.microsoft.com/en-us/library/Aa173557(SQL.80).aspx and
http://msdn2.microsoft.com/en-us/library/Aa176749(SQL.80).aspx ... if you
don't, you are in trouble, as MSDE does not provide the Rebuild utility
(rebuildm.exe) and the scripts to re-generate it.. if this is the case, you
have to uninstall and reinstall the MSDE instance.. you can or course keep
your user's databases files an re-attach them once re-installed..
regards
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Hey Andrea,
thx for the re. I was already afraid I would have to reinstall. It's the
instance from sharepoint. We do maintenance at a lot of customers and
some have full SQL versions so perhaps I could use the rebuildm tool
there. But reinstalling sharepoint and replacing the database STS and
STS_Config might be faster as I think those are the only ones that matter.
Anyways thanks again
Andrea Montanari wrote:
> hi,
> Freaky wrote:
> if you have a valid master database backup, you can restore it as indicated
> in http://msdn2.microsoft.com/en-us/library/Aa173557(SQL.80).aspx and
> http://msdn2.microsoft.com/en-us/library/Aa176749(SQL.80).aspx ... if you
> don't, you are in trouble, as MSDE does not provide the Rebuild utility
> (rebuildm.exe) and the scripts to re-generate it.. if this is the case, you
> have to uninstall and reinstall the MSDE instance.. you can or course keep
> your user's databases files an re-attach them once re-installed..
> regards
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!
CheckQueryProcessorAlive: sqlexecdirect failed
Hi,
I have the following error in my sql error log.
2004-05-05 09:44:34.23 spid3 SQL Server is terminating
due to 'stop' request from Service Control Manager.
I have the following error in my cluster log just before
my entry into the sql error log. Could you let me know
what could be the cause? The server load was not high and
the system was not running any dbcc at that time.
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = HYT00;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Timeout expired
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] OnlineThread: QP is not online.
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
08001; native error = b; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your
network documentation.
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
01000; native error = 274c; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake
()).
Operating System and Version: Windows 2000 Server SP4
Database: MSSQL2000 SP3
HARDWARE CONFIGURATION INFORMATION
Machine Type: HP Netserver LT6000R
Amount of RAM: 4 GB
Type of Network Card: HP NetServer 10/100TX PCI LAN
Adapter (Slot)
Disk Type & Size: 4 x 36GB
Controller(s): HP NetRAID-2M Controller
Integrated HP NetRaid
Tape Unit, make/model:
CD-ROM make/model: TEAC CD-224E
regards,
bharathThe cluster service was unable to connect to SQL Server to verify that it
was running. There are numerous reasons why this could happen. I then
shutdown SQL Server and, I assume, failed it over to the other node or
restarted on the same node.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have the following error in my sql error log.
2004-05-05 09:44:34.23 spid3 SQL Server is terminating
due to 'stop' request from Service Control Manager.
I have the following error in my cluster log just before
my entry into the sql error log. Could you let me know
what could be the cause? The server load was not high and
the system was not running any dbcc at that time.
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = HYT00;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Timeout expired
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] OnlineThread: QP is not online.
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
08001; native error = b; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your
network documentation.
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
01000; native error = 274c; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake
()).
Operating System and Version: Windows 2000 Server SP4
Database: MSSQL2000 SP3
HARDWARE CONFIGURATION INFORMATION
Machine Type: HP Netserver LT6000R
Amount of RAM: 4 GB
Type of Network Card: HP NetServer 10/100TX PCI LAN
Adapter (Slot)
Disk Type & Size: 4 x 36GB
Controller(s): HP NetRAID-2M Controller
Integrated HP NetRaid
Tape Unit, make/model:
CD-ROM make/model: TEAC CD-224E
regards,
bharathThe cluster service was unable to connect to SQL Server to verify that it
was running. There are numerous reasons why this could happen. I then
shutdown SQL Server and, I assume, failed it over to the other node or
restarted on the same node.
Rand
This posting is provided "as is" with no warranties and confers no rights.
CheckQueryProcessorAlive: sqlexecdirect failed
Hi,
I have the following error in my sql error log.
2004-05-05 09:44:34.23 spid3 SQL Server is terminating
due to 'stop' request from Service Control Manager.
I have the following error in my cluster log just before
my entry into the sql error log. Could you let me know
what could be the cause? The server load was not high and
the system was not running any dbcc at that time.
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = HYT00;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Timeout expired
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] OnlineThread: QP is not online.
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
08001; native error = b; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your
network documentation.
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
01000; native error = 274c; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake
()).
Operating System and Version: Windows 2000 Server SP4
Database: MSSQL2000 SP3
HARDWARE CONFIGURATION INFORMATION
Machine Type: HP Netserver LT6000R
Amount of RAM: 4 GB
Type of Network Card: HP NetServer 10/100TX PCI LAN
Adapter (Slot)
Disk Type & Size: 4 x 36GB
Controller(s): HP NetRAID-2M Controller
Integrated HP NetRaid
Tape Unit, make/model:
CD-ROM make/model: TEAC CD-224E
regards,
bharath
The cluster service was unable to connect to SQL Server to verify that it
was running. There are numerous reasons why this could happen. I then
shutdown SQL Server and, I assume, failed it over to the other node or
restarted on the same node.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have the following error in my sql error log.
2004-05-05 09:44:34.23 spid3 SQL Server is terminating
due to 'stop' request from Service Control Manager.
I have the following error in my cluster log just before
my entry into the sql error log. Could you let me know
what could be the cause? The server load was not high and
the system was not running any dbcc at that time.
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.050 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = HYT00;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Timeout expired
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] OnlineThread: QP is not online.
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
000006b4.000008bc::2004/05/05-09:43:16.066 SQL Server <SQL
Server>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server
Driver]Communication link failure
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
08001; native error = b; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]General network error. Check your
network documentation.
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] ODBC sqldriverconnect failed
000006b4.000008bc::2004/05/05-09:43:37.300 SQL Server <SQL
Server>: [sqsrvres] checkODBCConnectError: sqlstate =
01000; native error = 274c; message = [Microsoft][ODBC SQL
Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake
()).
Operating System and Version: Windows 2000 Server SP4
Database: MSSQL2000 SP3
HARDWARE CONFIGURATION INFORMATION
Machine Type: HP Netserver LT6000R
Amount of RAM: 4 GB
Type of Network Card: HP NetServer 10/100TX PCI LAN
Adapter (Slot)
Disk Type & Size: 4 x 36GB
Controller(s): HP NetRAID-2M Controller
Integrated HP NetRaid
Tape Unit, make/model:
CD-ROM make/model: TEAC CD-224E
regards,
bharath
The cluster service was unable to connect to SQL Server to verify that it
was running. There are numerous reasons why this could happen. I then
shutdown SQL Server and, I assume, failed it over to the other node or
restarted on the same node.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Friday, February 24, 2012
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?)
> >
> >
>
>
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?)
> >
> >
>
>
Sunday, February 12, 2012
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')
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')
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
> >
> >
> >.
> >
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
> >
> >
> >.
> >
Friday, February 10, 2012
Check the sql server service account
Hello!
I would need to check the name of the sql server service account from inside TSQL.
I had one idea about reading from the sysprocesses system table,
but that only gives me information about the SQL Server Agent service account.
Are there other ways?
(It has to work for both SQL Server 2000 and SQL Server 2005.)
Best regards
Ola Hallengren
There is an undocmented approach using 'registry key reading' in SQL Server 2000 version:
xp_regread @.rootkey='HKEY_LOCAL_MACHINE',
@.key='SYSTEM\ControlSet001\Services\SQLServerAgent',
@.value_name='ObjectName'
I'm working onSQL 2005 and will post here once it is successful.
Subscribe to:
Posts (Atom)