Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Service Broker / March 2008

Tip: Looking for answers? Try searching our database.

sys.conversation_endpoints

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Al - 26 Feb 2008 11:13 GMT
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.
Al - 28 Feb 2008 01:04 GMT
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

> First question, at what point are entires removed from the
> sys.conversation_endpoints system view?
[quoted text clipped - 11 lines]
>
> Any answers / help greatly appreciated.
Simon Sabin - 07 Mar 2008 09:00 GMT
Hello Al,

You need to make sure you end the conversation on both ends.

The conversation end points stick around to make sure the same messages can't
be resent.

Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> OK, if we specify a "lifetime" of the conversation, and end (close)
> the conversation within the lifetime, then the
[quoted text clipped - 18 lines]
>>
>> Any answers / help greatly appreciated.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.