First off, I apologize for not responding to this thread earlier. I did not have an account at the forum and recently created one.

Not sure if any commercial scale applications have yet been developed using Service Broker, but I remember Roger Walter writing a few articles about the same and also delivering a few webcasts.

Here is one article about some use cases: http://msdn.microsoft.com/sql/archive/default.aspx?pull=/library/en-us/dnsql90/html/sql2k5_SrvBrk.asp

First off, I apologize for not responding to this thread earlier. I did not have an account at the forum and recently created one.

Service Broker messages are always sent to a service. Each service is associated with a queue and each queue can have an activation procedure that wakes up when messages arrive at the queue. You can also specify the maximum number of activation procedures that Service Broker can instantiate for the queue.

First off, I apologize for not responding to this thread earlier. I did not have an account at the forum and recently created one.

Service Broker can basically be used to achieve asynchronous semantics in the database. In your case, the application tier receives messages from an external source and if you are not using transactional messaging in MSMQ, the performance of SSB and MSMQ is comparable. Also, in your case, if the application tier is load-balanced, you will have multiple Q's doing the job. I would not recommend replacing this solution with SSB because, if you need to do some pre-processing of the Q before executing the SP, then you cannot do it. Also, by using MSMQ in this case, you can have other applications that can also drain the Q.

SSB is largely for writing reliable, asynchronous, message oriented database applications.

First check if the ReceiverQueue itself has any message. If not, check the sys.transmission_queue to see if any errors are logged. One other post that I made had a user with a similar problem and the sys.transmission_queue had a message indicating an error about a missing database master key. If you see a similar error, you can solve it using the method that I've outlined in: http://blogs.sqlxml.org/srinivassampath/archive/2005/06/19/3457.aspx

Hello, great article, compact & clear. On my june CTP version, it didn't seem to work without the following change (maybe update the article ? )

DECLARE @conversationHandle UNIQUEIDENTIFIER
DECLARE @message NVARCHAR(100)

BEGIN
  BEGIN TRANSACTION;
  BEGIN DIALOG @conversationHandle
        FROM SERVICE Sender
        TO SERVICE 'Receiver'
        ON CONTRACT HelloContract WITH ENCRYPTION=OFF, LIFETIME= 600;
  -- Send a message on the conversation
  SET @message = N'Hello, World';
  SEND  ON CONVERSATION @conversationHandle
        MESSAGE TYPE HelloMessage (@message)
  COMMIT TRANSACTION
END
GO

regards,

steph

Hello

I too am having problems getting this sample to work.

I created a db called TestDb.

I then pasted the sample service broker code (with your ENCRYPTION change)

into the mgmt studio. I modified the USE statement at the top.

There is never anything in the ReceiverQueue.

Everyone tries their sample code against the AdventureWorks db. I suspect that

db has some property set that we are not being told about.

Could you try the sample code after you create a new database.

Thanks.

hbatra -

I have just developed a C# app that does exactly what you explained (ie, writes from an MSMQ queue to a SQL Server table).  Do you mind sharing how you run this app?  As a scheduled task, a job in SQL Server, a service???  Just wondering.  Thanks.

Steve

Nice article, but I'm not getting anything when I execute posted code.

Does anybody have an idea why?

Thanks