tag:blogger.com,1999:blog-4545163587452304025.post6834399883953796411..comments2023-10-24T10:54:02.185+03:00Comments on Dieg's world: Asynchronous triggers using SQL BrokerDieghttp://www.blogger.com/profile/15977769850127757216noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-4545163587452304025.post-82727802845937229052017-04-29T21:08:49.343+03:002017-04-29T21:08:49.343+03:00See the queue creation statementSee the queue creation statementDieghttps://www.blogger.com/profile/15977769850127757216noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-77655512894107972322017-04-28T20:08:17.710+03:002017-04-28T20:08:17.710+03:00you execute the stored procedure and then it reads...you execute the stored procedure and then it reads the queue, right? I don't see anything that automatically runs the stored procedure.RaleighMarkhttps://www.blogger.com/profile/13927664169095245679noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-13400949086300317472014-03-03T01:29:36.880+02:002014-03-03T01:29:36.880+02:00Hi guys im trying exactly as posted here, i see th...Hi guys im trying exactly as posted here, i see the message in the SampleQueue but the store procedure never gets called or executed, i placed a print on top of the SP to check it's getting hit but nothing gets printed, no errors, im lost, can you please help me out?Anonymoushttps://www.blogger.com/profile/15140851924883941400noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-10357692313708877532013-05-02T20:30:20.239+03:002013-05-02T20:30:20.239+03:00if you implemented the spMessageProcSample it gets...if you implemented the spMessageProcSample it gets the messages from the queue..add some insert command in "--process xml message here..." to see if it works or not.Dieghttps://www.blogger.com/profile/15977769850127757216noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-89961129360605689502013-04-24T22:52:04.296+03:002013-04-24T22:52:04.296+03:00 Hey, everything seems to have been created/config... Hey, everything seems to have been created/configured correctly, but when my trigger fires, nothing goes into the queue, and the target stored proc is never called. I followed your example directly, and the service broker is enabled. Any thoughts on what I might be missing? Thanks!RambleCampbellhttps://www.blogger.com/profile/12095633640995375851noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-72931085132405987712012-10-22T22:21:07.093+02:002012-10-22T22:21:07.093+02:00I am not sure what you are trying to accomplish by...I am not sure what you are trying to accomplish by this design, but theoretically you can run any tsql in the 'spMessageProcSample' procedure. In your case it means that you would run this SSIS package for every trigger call - as I said - I don't understand what you are trying to accomplish but it sounds like a risky idea, in addition - allowing xp_cmdshell is a known security risk.Dieghttps://www.blogger.com/profile/15977769850127757216noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-22276848677186101282012-10-22T10:22:56.186+02:002012-10-22T10:22:56.186+02:00Sorry....I meant if I write the above code in the ...Sorry....I meant if I write the above code in the Trigger an Execute it in the Procedure.Vinu Vijayannoreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-61809358958666041442012-10-22T09:55:14.347+02:002012-10-22T09:55:14.347+02:00Can I write the following code in the procedure an...Can I write the following code in the procedure and execute it in the procedure to execute a SSIS Package from it?:<br /><br />SET @MessageBody = 'EXEC xp_cmdshell ''dtexec /FILE "C:\Documents and Settings\Administrator\Desktop\Test\Test\Test1.dtsx" /decrypt saa'' ) '<br /><br />Or does this only work for Inserts/Updates into another table??Vinu Vjayannoreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-75147645716995668192012-10-02T23:41:32.405+02:002012-10-02T23:41:32.405+02:00The procedure runs for every trigger call. Can you...The procedure runs for every trigger call. Can you be more specific on what seem to be the problem?Dieghttps://www.blogger.com/profile/15977769850127757216noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-50915719916947694282012-10-02T09:04:36.104+02:002012-10-02T09:04:36.104+02:00I have tried this but the stored procedure is runn...I have tried this but the stored procedure is running twice.Diodehttps://www.blogger.com/profile/17706294910220697551noreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-24000103626626684772011-04-18T02:19:46.659+03:002011-04-18T02:19:46.659+03:00Thanks Diego, good stuff!Thanks Diego, good stuff!Alanhttp://www.arizonariding.comnoreply@blogger.comtag:blogger.com,1999:blog-4545163587452304025.post-41732584180313494392010-06-07T16:31:40.314+03:002010-06-07T16:31:40.314+03:00Added "AUTHORIZATION dbo" to messageType...Added "AUTHORIZATION dbo" to messageType, contract & services creation script.<br />Read: <a href="http://diegworld.blogspot.com/2010/06/sqlbroker-clean-up.html" rel="nofollow">SqlBroker cleanup</a> for more details.Dieghttps://www.blogger.com/profile/15977769850127757216noreply@blogger.com