Thursday, September 28, 2006 - Posts

Service Broker - Objects reside in each database

My blog has moved to sqlblogcasts.com/blogs/simons
The full version of this post can be found here., http://sqlblogcasts.com/blogs/simons/Service Broker - Objects reside in each database
The new RSS feed is here

One thing you learn very early on with Service Broker is that even though Services and Contracts at first may appear to be server wide configuration, they are actually database objects.

This makes sense as the service broker objects relate to a function i.e. application and the level of granularity for backing up and maintaining such a function is a database.

However the difference between normal objects and Service Broker objects (apart from the case sensitivity) is that when you create Service Broker objects you can't specify the database or a schema. This means you have to be in the database you want to create the objects when you execute your CREATE statements.

... To read the complete version of this post go here, http://sqlblogcasts.com/blogs/simons/Service Broker - Objects reside in each database

Service Broker - Clean up your transmission queue

My blog has moved to sqlblogcasts.com/blogs/simons
The full version of this post can be found here., http://sqlblogcasts.com/blogs/simons/Service Broker - Clean up your transmission queue
The new RSS feed is here

This isn't about changing your air filter, spark plugs or oil. Its about what to do when, like me, you don't get things right first time.

If developing Service Broker applications and you misspell your services, forget to create a master key, or do any of the many things that result in your messages not being delivered, then your transmission queue will fill up.

... To read the complete version of this post go here, http://sqlblogcasts.com/blogs/simons/Service Broker - Clean up your transmission queue

Service Broker - Grouping conversations

My blog has moved to sqlblogcasts.com/blogs/simons
The full version of this post can be found here., http://sqlblogcasts.com/blogs/simons/Service Broker - Grouping conversations
The new RSS feed is here

In my investigation of service broker as an synchronous engine I wanted to be able to put messages on a queue and then for a batch process to take them off again.

What I however found was that if a message is sent to a service i..e from a trigger, then when my batch process receives from the queue it only gets the one message. This I can understand but thought there must be a way around it.

... To read the complete version of this post go here, http://sqlblogcasts.com/blogs/simons/Service Broker - Grouping conversations