I have done some performance testing to see if asynchronous triggers performs any better than synchronous triggers in a simple audit scenario -- capturing record snapshots at insert, update and delete events to a separate database within the same instance of SQL Server.

Synchronous triggers performed 50% better than asynchronous triggers; this was with conversation reuse and the receive queue activation turned off, so the poor performance was just in the act of forming and sending the message, not receiving and processing.  This was not necessarily surprising to me, and yet I have to wonder under what conditions would we see real performance benefits for audit scenarios.

I am interested if anyone has done similar testing, and if they received similar or different results.  If anyone had conditions where asynchronous triggers pulled ahead for audit scenarios, I would really like to hear back from them.  I invite any comments or suggestions for better performance.

The asynchronous trigger:

The synchronous trigger:

Hi,

I have set up SB between 2 databases, and I keep geting a variety of error messages in the queue on both sides. The first is:

 An error occurred while receiving data: '10054(error not found)'.

And on the other side its

Service Broker received an error message on this conversation. Service Broker will not transmit the message; it will be held until the application ends the conversation.

The only difference between this and the tutorials is that the TCP port have been moved to 4321 instead of 4022, and this has been done both sides, because something else was blocking the 4022 port. This one is definately free on both sides. I have recreated the certificates, the users, the end points, the queues and the services multiple times, and checked them all in the sys.routes etc and they all seem fine.

I do also get a message in the queue that I can receive sometimes that tells me I don't have rights to the service on the other machine. I can send a message to itself and it doesn't complain.

Both machines are on the same domain, and I have also tried to grant rights to public to no avail.

Help!

TIA

Ian.

Hi

I am getting below error on a long running query crashing the app, even though I am running the query as background task;

ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x623978 to COM context 0x623ae8 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

The code is below. How can I fix the 'ContextSwitchDeadlock was detected' issue please?

    Function ExecuteSQL(ByVal St As String) As Boolean

        Try

            Try

                Dim result = ExecuteSQLAsync(DBCommand)
                I = result.Result

            Catch ae As AggregateException

                For Each ex In ae.InnerExceptions
                    Throw
                Next

            End Try

            Return True

        Catch ex As SystemException

            MsgBox(ex.Message)

            Return True

        End Try

    End Function


    Async Function ExecuteSQLAsync(DBCommand As SqlCommand) As Task(Of Integer)

        Dim x = Await DBCommand.ExecuteNonQueryAsync()

        Return x

    End Function

Thanks

Regards

Hello, I would need help in configuring Service broker. As both servers are on the intranet, I wanted to remain the most simple so I used no certificates and allowed anonymous access but still, using SSBDiagnose, I can see errors.

I would like to paste here my configuration and my usage of SSBDiagnose, I already asked a question about SSBDiagnose usage but this new question is rather on the usage of certificates and the configuration of SSB, for me to know if I am doing this in the best possible way.

Reading on the web, I have read in few places that certificates are not mandatory and that Windows Authentication only can be used. Then, I read that even if endpoints don't request certificates, the communication between two servers will still requires certificates so I am wondering where is the truth... 

I have two servers:

• EmployeesSvr (SQL Server 2012 Enterprise Edition with Always On, EmployeesSvr is the listener name in front of two virtual servers)

	CREATE MESSAGE TYPE [//E/S/ETChanged] VALIDATION = WELL_FORMED_XML
	CREATE CONTRACT [//E/S/ECContract] ([//E/S/ETChanged] SENT BY INITIATOR)
	CREATE QUEUE [dbo].[ECQueue] WITH STATUS = ON , RETENTION = OFF , ACTIVATION (  STATUS = ON , PROCEDURE_NAME = [dbo].[SSB_ECQueueProc] , MAX_QUEUE_READERS = 1 , EXECUTE AS N'dbo'  )
	CREATE SERVICE [//E/S/ECService]  ON QUEUE [dbo].[ECQueue] ([//E/S/ECContract])

	CREATE ROUTE [RouteToSECService]   WITH  SERVICE_NAME  = N'//S/S/ECService' ,  BROKER_INSTANCE  = N'F...' ,  ADDRESS  = N'TCP://SoftwaresSrv.test.com:4022' 
	CREATE REMOTE SERVICE BINDING [SECServiceBinding]  TO SERVICE N'//S/S/ECService'  WITH USER = [domain\SvcBrokerTestUser] ,  ANONYMOUS = ON 
	CREATE ENDPOINT [ESBEndpoint] STATE=STARTED AS TCP (LISTENER_PORT = 4022, LISTENER_IP = ALL) FOR SERVICE_BROKER (MESSAGE_FORWARDING = DISABLED, MESSAGE_FORWARD_SIZE = 10, AUTHENTICATION = WINDOWS NEGOTIATE, ENCRYPTION = DISABLED)

• SoftwaresSvr (SQL Server 2008 R2)

	CREATE MESSAGE TYPE [//E/S/ETChanged] VALIDATION = WELL_FORMED_XML
	CREATE CONTRACT [//E/S/ECContract] ([//E/S/ETChanged] SENT BY INITIATOR)
	CREATE QUEUE [dbo].[ECQueue] WITH STATUS = ON , RETENTION = OFF , ACTIVATION (  STATUS = ON , PROCEDURE_NAME = [dbo].[SSB_ECQueueProc] , MAX_QUEUE_READERS = 1 , EXECUTE AS N'dbo'  )
	CREATE SERVICE [//S/S/ECService]  ON QUEUE [dbo].[ECQueue] ([//E/S/ECContract])
	CREATE ROUTE [RouteToECService]   WITH  SERVICE_NAME  = N'//E/S/ECService' ,  BROKER_INSTANCE  = N'2...' ,  ADDRESS  = N'TCP://EmployeesSvr.test.com:4022' 
	CREATE REMOTE SERVICE BINDING [EECServiceBinding]  TO SERVICE N'//E/S/ECService'  WITH USER = [domain\SvcBrokerTestUser] ,  ANONYMOUS = ON 
	CREATE ENDPOINT [SSBEndpoint] STATE=STARTED AS TCP (LISTENER_PORT = 4022, LISTENER_IP = ALL) FOR SERVICE_BROKER (MESSAGE_FORWARDING = DISABLED, MESSAGE_FORWARD_SIZE = 10, AUTHENTICATION = WINDOWS NEGOTIATE, ENCRYPTION = DISABLED)

• My SSBDiagnose command :

ssbdiagnose -E CONFIGURATION 
	FROM SERVICE //E/S/ECService 
	-S EmployersSvr 
	-d EmployersDB 
TO SERVICE //S/S/ECService 
	-S SoftwaresSvr 
	-d SoftwaresDB 
ON CONTRACT //E/S/ECContract

• The result :

Microsoft SQL Server 10.50.1600.1
Service Broker Diagnostic Utility
D  29978 EmployersSvr     EmployersDB             
	No valid certificate was found for user domain\SvcBrokerTestUser

D  29977 SoftwaresSvr  SoftwaresDB 
	The user domain\SvcBrokerTestUser from database EmployersDB on EmployersSvr cannot be mapped into this database using certificates

D  29933 SoftwaresSvr  SoftwaresDB 
	The routing address TCP://EmployeesSvr.test.com:4022 for service //E/S/ECService does not match any of the IP addresses for EmployersSvr 

	An internal exception occurred: An exception occurred while executing a Transact-SQL statement or batch.

Thank you for any help, I am searching for several answers :

1. Can I use the setup as I defined, with no certificate ?  Is it risky ?
2. Is there too many objects defined ?  Is it mandatory to have a Route and a Remote Service Binding ?  I don't understand how those two are working togheter...
3. Is it ok to use the same windows account on each side, do they only need an 'Open' access rigth or do they need to be db_owner ?

Best regards,

Claude

I would like to execute stored procedure after some time from now.
So, i have created queue and service:

CREATE QUEUE [dbo].[StartSAQueue] WITH STATUS = ON , RETENTION = OFF , ACTIVATION (  STATUS = ON , PROCEDURE_NAME = [dbo].[p_test_queue] , MAX_QUEUE_READERS = 1 , EXECUTE AS N'dbo'  ), POISON_MESSAGE_HANDLING (STATUS = ON) 

CREATE SERVICE [SAService]  ON QUEUE [dbo].[StartSAQueue] 
CREATE PROCEDURE dbo.p_test_queue
AS
DECLARE @Handle UNIQUEIDENTIFIER, @MessageType SYSNAME, @message NVARCHAR(255), @stevec INT;
RECEIVE TOP (1) @Handle = conversation_handle, @message=message_body FROM dbo.StartSAQueue;

IF @Handle IS NOT NULL
BEGIN  
END CONVERSATION @Handle;
INSERT INTO test.[dbo].[testQueue]([message]) VALUES(@message)
END

Now i start conversation:

DECLARE @DialogHandle UNIQUEIDENTIFIER;
DECLARE @RequestMessage XML;

BEGIN dialog CONVERSATION @DialogHandle FROM SERVICE [SAService] TO SERVICE N'SAService', 'current database' WITH ENCRYPTION = OFF;

SET @RequestMessage = N'<Request><SA>58</SA></Request>';

SEND ON CONVERSATION @DialogHandle(@RequestMessage);

It works.
Now i would like to execute this procedure after 10 minutes:

BEGIN CONVERSATION TIMER(@DialogHandle) TIMEOUT = 600;

It works. But how can i add message to this conversation? If I try this, it raises error:

BEGIN CONVERSATION TIMER(@DialogHandle(@RequestMessage)) TIMEOUT = 600;

I've come across a strange behaviour in T-SQL script I have written and which I can recreate with the Service Broker Tutorial athttp://technet.microsoft.com/en-us/library/cc281528(v=sql.105).aspx where I have modified the code to dump Initiator and Target queue contents to a separate table (together with a timestamp and description of where in the code the dump occurs) so I can examine their contents at leisure. Code can be provided if needed..

Discussing the tutorial (which still applies to my script as well):-

1. Initiator begins dialog and sends a meassage. This populates the Target queue.

2. Stored procedure fires and executes as a result of the Target queue being populated.

3. Stored procedure execution - receives the message (Target queue now contains no rows).

4. Stored procedure execution - determines correct message type and sends a message which populates the Initiator queue.

5. The row is held in the Initiator Queue until we 'Receive' it.

Everything is fine and is as expected. However, here is the wrap...

At step 4, at exactly the same time the Initiator queue is populated, the stored procedure fires and executes again (with a different SPID). Don't forget, we haven't Received the message from the Initiator queue yet and is not as a result of intitiator 'ending conversation'. In fact, at this time the Target queue is empty and the check in the stored procedure for 0 row count when 'Receiving' from the queue prevents further messages being sent from the stored procedure.

Is this normal behaviour that the stored procedure executes whenever EITHER queue is populated even though we have defined only the Target queue as the internal activator?

I would like to get the last row from every order and the quantity of the last row but one:

SELECT o.order_id, o.order_user, o.Q,
Q_before=(SELECT TOP 1 Q FROM dbo.orders WHERE order_id=o.order_id AND order_date<o.order_date 
ORDER BY order_date DESC)
FROM dbo.Orders AS o

How can this be done with new functions in SQL 2012?

I have successfully set up external activation in service broker to execute an ssis package. My issue is that I currently can only execute the ssis package once.

On dropping the first message the package executes and logs back to my database. When I drop another message nothing occurs. Nothing logs to the database, event viewer, sql log, or the sbea easervice log. I know there are threadiong concerns with ea and ssis; but even when I kill existing messages and purge the queue I cannot execute the package.

However if I tear down the EA queues and activation then rebuild it again (using a script) the package will fire again.

I am somewhat perplexed and I am hoping that someone in the community may have a resolution.

Cheers

I'm using Event Notification in SQL Server 2008 R2.    I'm trying to clear messages in a queue which has retention = ON without ending conversation.  

For testing purpose, I have tried to clear messages in the queue using end conversation but that will delete the event notification.

I am completely new to Service Broker. I got introduced to it indirectly when learning SQL Server Cache Dependency for ASP.NET data caching.  When running a code sample a Service and Queue were created on development database. I am done with this sample but I still see recurring "BEGIN CONVERSATION..." and "WAITFOR(RECEIVE TOP (1)..." queries (every minute or so) for this database in SQL Server profile. Such queries do not appear for any other database.

After taking a closer look I found there is a queue and a service under "Service Broker" for this database. I deleted them both but the queries didn't stop and after checking again I see that they somehow got re-created "automagically".

Hot to get rid of them completely?

Hello, 

I have a table trigger that sends a message to a service broker queue when a record is updated.  The queue kicks off a stored procedure that then schedules a run of an SSIS package that then stages the updates to be consumed by another application.  What I am finding is that a record can be updated multiple times while messages are waiting in the queue consumed and processed.  This is causing multiple messages for the same record, which then causes redundant and often contentious processing. Should I simply query the queue for messages containing the record ID and if one exists, skip adding another message?  It seems to me that I will run into timing issues with such an approach. 

Thank you very much for any direction shared.

...Rob

Hello,

I recently setup Service Broker - Internal Activation. I ran built-in SSMS "Service Broker Statistics" reports and saw this;

Store Procedures Invoked/sec : 184

Tasks Aborted/sec :184

Tasks Running: 0

Tasks Started/sec: 184

I used "SET XACT_ABORT ON" at the top of the activation sproc. Do you think all transactions through  the activation sproc are rolling back?

Thanks,

Kuzey

Hello

I tried for hours to get my notifications working, without success, on SQL Server 2008R2 Web Edition 64b

I send mail with the test :

USE msdb
GO
EXEC sp_send_dbmail @profile_name='ARRIERE',@recipients='mai@mail.tld',
@subject='Bonjour ',@body='Congrates Database Mail Received By you Successfully.'

But this mail seems to be never sent.

With:

EXEC msdb.dbo.sysmail_help_queue_sp @queue_type = 'mail';

The queue state is always INACTIVE, and length is growing everytime I send a email.

I tried to restart the mail system some times :

EXEC msdb.dbo.sysmail_stop_sp;
EXEC msdb.dbo.sysmail_start_sp;

The states goes RECEIVE OCURRING, but after some seconds and without intervention, it goes back to INACTIVE.

I tried to rester SQL Agent, SQL Server, the server himself, but no luck.

The broker is activated (SELECT is_broker_enabled FROM sys.databases WHERE name = 'msdb' ;)

I disabled every firewall, antivirus and others (by the way, I can do "telnet smtp.domain.tld 25" and send a mail with telnet.

With

SELECT * FROM msdb.dbo.sysmail_allitems;

I see all my mails with state "unsent".

Nothing logged in Event Viewer, SQL Events, and in sysmail_event_log I only get "Activation successful".

I configured the local IIS SMTP as a relay as said here : http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/f9744284-a9b6-4bfb-81b9-c4833f282ad0 

I cleaned the mails with:

DECLARE @GETDATE datetime
SET @GETDATE = GETDATE()
EXECUTE msdb.dbo.sysmail_delete_mailitems_sp @sent_before = @GETDATE;
GO

=> Nothing more.

Can I do something more?

Thans for your help.

Regards

I'm using a timer to call the procedure after 15 minutes.

DECLARE @DialogHandle UNIQUEIDENTIFIER;
BEGIN dialog CONVERSATION @DialogHandle FROM SERVICE [myService] TO SERVICE N'myService', 'current database' WITH ENCRYPTION = OFF;
BEGIN CONVERSATION TIMER(@DialogHandle) TIMEOUT = 900;

This is from MSDN:

Starts a timer. When the time-out expires, Service Broker puts a message of type http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer on the local queue for the conversation.

What i would like to do is to add some custom message (or activate procedure with some parameter value).
If i try to create message and sends it, it won't work:

DECLARE @RequestMessage XML;
SET @RequestMessage = N'<Request><SA>58</SA></Request>';
BEGIN dialog CONVERSATION @DialogHandle FROM SERVICE [myService] TO SERVICE N'myService', 'current database' WITH ENCRYPTION = OFF;
BEGIN CONVERSATION TIMER(@DialogHandle(@RequestMessage)) TIMEOUT =900;

Is there some other way to get some values when my procedure is activated?
I can insert dialogHandle and some values into some table when starting timer and when procedure is activated read this values from table but I guess there should be some more simplify way?

br, Simon

I found every several minutes, sometimes one or twice in an hour, I still get a dozen error like below logged in SQL Log.  See the error is "You do not have permission to access the service". I found some articles on other errors, but nothing about this error.  I want to get more information on this, and a way to trace what is the permission about and which user doesn't have the permission.

Source  spid26s

Message
The query notification dialog on conversation handle '{E6FC299F-8BFE-DC11-A4E1-000D5670268E}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8494</Code><Description>You do not have permission to access the service &apos;SqlQueryNotificationService-9ff8b39d-90a8-45bc-83a7-23837920774d&apos;.</Description></Error>'.

thanks

Hi, 

I have configured 2 SQL instances to exchange messages with service broker. I used certificate authentication and no encryption. Then SP is executed to send a message on Source server I see:

1. sys.transmission_queue I see my messages but transmission_status is EMPTY. But I see other messages for another SB configuration that are failed (this is another story). Could this cause my messages are not been send?

2. SQL Profiler only three messages available
1) BEGIN DIALOG
2) SEND Message
3) Remote  - Method name: tcp://remote_server:4030
4) Next message should be connected - be no connection made....

On Destination server SQL Profiler - nothing. sys.transmission - nothing.

How to troubleshoot this issue?

Thanks

Hi All,

One of my client/customer is asking us to set up SERVICE BROKER QUEUE SIZE job, is the customer really intend about creating job for  SERVICE BROKER QUEUE SIZE, if so how to create job for this?

Hello everyone,

I am working on a demo for my devs/dba at work regarding the use of service broker, why we should start using it, and other fun facts that just go above initial implementation.  Part of this demo includes the routing capabilities for cross instance conversations. 

The good news is that I get messages to from Instance A to Instance B.  The issue I am having is after receiving the message on Instance B, I send a response back, and that is failing.  For the life of me, I cannot figure out why.  The error I am receiving is:

"The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied."

In doing research on Google/Bing/Yahoo/Various Forums, the consensus seems to be that this is usually an issue with either A) Remote Service Binding or B) Case Sensitivity when specifying the server.  Maybe I have been looking at this code to long, but I cannot find an issue with either of these as I currently understand them.  So, I am looking for help.

Here are the full scripts that I am running.  Please note that these scripts are not configured to run all the way through, but in blocks.  I apologize for this in advance.

ServerA Script:
https://onedrive.live.com/redir?resid=ED3BB9E286990092!250&authkey=!AHr6nNdQgxnCYiQ&ithint=file%2ctxt

ServerB Script:
https://onedrive.live.com/redir?resid=ED3BB9E286990092!249&authkey=!AB_TXg0S2Rgwa38&ithint=file%2ctxt

I am using a VM, where I have installed 2 instance of SQL Server 2012 Developer Ed, SP2, CU1.  Instance1 is call ServerA.  Instace2 is called Server2. 

Thank you very much for any assistance you are able to provide. 

Sincerely,

Nathan Heaivilin

Hello, I got this error message. The server is experiencing issue of service broker suddenly stopping, so we are ruling out all errors at this point. Server is setup with HADR.

Win Server 2008 R2 Ent SP1

SQL 2012 11.0.3349 Ent

Thanks.