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 / February 2007

Tip: Looking for answers? Try searching our database.

Thread preview
Titles only
Unanswered
Popular
ThreadLast Post  Replies
Service Broker messages stuck in sys.transmission_queue28 Feb 2007 01:05 GMT1
I'm testing service broker on two machines in the same domain. I'm using
windows authentication. When I begin a dialog on serverA the message is
immediately put into the sys.transmission_queue with a blank
transmission_status, and is_conversation_error = 0. Also, I specified the
Service Broker and SQL 2005 Express23 Feb 2007 00:49 GMT3
I was just checking the SQL 2005 Features Comparison and for Service Broker
on SQL 2005 Express Edition it has a footnote saying that it is for
Subscriber only. Does this mean that it is not possible to initiate a
Service Broker application from a machine runing 2005 Express?
2008DecNovOctSepAugJulJunMayAprMarFebJan
2007DecNovOctSepAugJulJunMayAprMarFebJan
2006DecNovOctSepAugJulJunMayAprMarFebJan
2005DecNovOctSepAugJulJunMayAprMarFebJan
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread



©2008 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.