Method to check the connection status of any Machine on Network

Hello All:
I need to know the connection status of any machine on domain i.e. I want to
check that whether the machine is on or off(alive/dead).
If anyone can tell then I shall be highly grateful
Sincerely,
Adnan KudiyaHi
Try sp_who 'active'
"adnankudiya" <adnankudiya.1nq9tv@.mail.codecomments.com> wrote in message
news:adnankudiya.1nq9tv@.mail.codecomments.com...
> Hello All:
> I need to know the connection status of any machine on domain i.e. I
> want to check that whether the machine is on or off(alive/dead).
> If anyone can tell then I shall be highly grateful
> Sincerely,
> Adnan Kudiya
>
> --
> adnankudiya
> ---
> Posted via http://www.codecomments.com
> ---
>|||Hi
I assume you mean database connection status and not just something like
pinging the client periodically to see if you get a reply? This may be
difficult as you can gather information about when a connection last did
something sysprocesses, but you don't know if they are connected or have
died. If your application has a set timeout and any activity has not happene
d
in that time, I guess you can assume they are dead.
John
"adnankudiya" wrote:

> Hello All:
> I need to know the connection status of any machine on domain i.e. I
> want to check that whether the machine is on or off(alive/dead).
> If anyone can tell then I shall be highly grateful
> Sincerely,
> Adnan Kudiya
>
> --
> adnankudiya
> ---
> Posted via http://www.codecomments.com
> ---
>|||I thought about this a while back and did not come up with a good solution.
One idea was to write a stored procedure - sp_ping and execute that on the
connection:
create proc sp_ping
as
return 0
go
or something trivial and similar - EG
SELECT DateNow = GetDate()
You could run that SP with a timeout that is quite low say 2 seconds.
- Tim
BTW: I do realise sp_ is not a good prefix.
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:F32C6F92-2896-4F96-9FC5-49D846A434FF@.microsoft.com...
> Hi
> I assume you mean database connection status and not just something like
> pinging the client periodically to see if you get a reply? This may be
> difficult as you can gather information about when a connection last did
> something sysprocesses, but you don't know if they are connected or have
> died. If your application has a set timeout and any activity has not
> happened
> in that time, I guess you can assume they are dead.
> John
> "adnankudiya" wrote:
>

Messages in the sys.transmission_queue for a disable queue

I may have a misunderstanding of how SB works, but this seems like a problem.

If a queue is disable (i.e. status = off) and a message is sent to the queue the message is placed on the sys.transmission_queue. Once the queue is enabled I thought the messages were sent to the queue in the order they were placed on the sys.tranmission_queue? I have been troubleshooting a problem and this is not the case. Do I have a misunderstanding of how the sys.transmission_queue works?

The queue has retention turned off.

Messages are delivered in order within each conversation (RECEIVE cannot return msg 2 before msg 1 for any conversation). But the order of messages in the xmit queue does not determine in any way the order of which messages are actually being delivered.

HTH,
~ Remus

|||

If you have a scenario where you want to send a message to a service broker queue that updates a row in a table and then later you would like to send another message to do another update to the row in the same table and the queue is disabled before the first send there is no way to guarantee these messages will be processed in order they were sent? It sounds like unless you actually end up on the queue itself there is no gurantee in what order the xmit queue will deliver them to the queue. Am I correct?

Thanks for the help

|||

If the order matters, you must deliver them using the same conversation. Otherwise you are never quaranteed anything about the order and you can hit the xmit queue for other reasons that target queue disabled (low memory, a lock bounce etc)