HostWeb Forums » Microsoft Databases » microsoft.public.sqlserver.servicebroker » sys.conversation_endpoints

Topic: sys.conversation_endpoints

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 2/26/2008 4:13:02 AM

By: Anonymous
First question, at what point are entires removed from the
sys.conversation_endpoints system view?
As there is a status of CLOSED, I'm assuming that it doesn't occur when the
converation has been ended by both sides of the dialogue, otherwise when
would an entry go into that status?

The second question (and problem), is that we have a situation in which the
target sys.conversation_endpoints view is just growing in size, and all the
entries are in the CLOSED state (processing is for a single message in a
dialogue, and processed immediately). By the initiators
sys.conversation_endpoints is empty. Is this normal behaviour?
I should also say that in this enviroment we have seperate SQL Servers,
within the same Domain, each running under a different domain account.

Any answers / help greatly appreciated.

Replies below ↓

Replies

Reply | New Topic | This is SPAM | This is Offensive

Submitted: 2/27/2008 6:04:00 PM

By: Anonymous

RE: sys.conversation_endpoints

OK, if we specify a "lifetime" of the conversation, and end (close) the
conversation within the lifetime, then the sys.conversation_endpoints entry
is removed about 30 mintues after the conversation was due to expire

"Al" wrote:

> First question, at what point are entires removed from the
> sys.conversation_endpoints system view?
> As there is a status of CLOSED, I'm assuming that it doesn't occur when the
> converation has been ended by both sides of the dialogue, otherwise when
> would an entry go into that status?
>
> The second question (and problem), is that we have a situation in which the
> target sys.conversation_endpoints view is just growing in size, and all the
> entries are in the CLOSED state (processing is for a single message in a
> dialogue, and processed immediately). By the initiators
> sys.conversation_endpoints is empty. Is this normal behaviour?
> I should also say that in this enviroment we have seperate SQL Servers,
> within the same Domain, each running under a different domain account.
>
> Any answers / help greatly appreciated.

Contents
Home
Forums
About Us
Contact Us
Web Hosting:
Hosting Providers
How to choose a name
What is a Hosting Provider
Hosting Types
Choosing the right plan
 
Search
 
Login to HostWeb.com
Email
Password
If you do not have an account with us yet, join now - it's FREE!