Service Broker question -- sql server notification services

Sean
7/29/2006 9:18:01 AM

1. is this the best place to ask a service broker question?

Forgive me Service Broker experts I am speaking outside of my realm here.
Is it possible that a component â€œtypeâ€ could automatically creates a
â€œconversationâ€ in the Service Broker and if not well designed that
conversation gets stuck and never closes. So specifically I have a component
â€œtypeâ€ (meaning not one particular instance but the class itself) and anytime
I reference Update to a specific table with a sproc of any signature I get
the exact same error which looks to me that it is refereeing to an old sproc.
The basic error is that to many parameters are being specified which is
because the table contains one extra column then the old sproc however I have
created sprocs with only a few parameters and get the same error.

Now granted it could be a developer error on any infinite levels however I
ask a favor. That favor is to assume I have done my part correctly and that
the problem does lie somehow within SQL 2005 itself. Not saying I am wrong,
just saying at this point I need to get a deep understanding of all
possibilities at the SQL 2005 level first.
Thanks!

Remus Rusanu [MSFT]
8/3/2006 8:27:10 AM

There is a Service Broker newsgroup at
microsoft.public.sqlserver.servicebroker and a Service Broker forum at
http://forums.microsoft.com/msdn/showforum.aspx?forumid=91&siteid=1

Yes, it is possible that an application to have bugs and create
conversations that stuck forever. But the dba has means at its disposal to
clean up such stuck conversations. The fix is, of course, to fic the
application.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx

[quoted text, click to view]

sql server notification services : Service Broker question