|
|
Posted by Tibor Karaszi on 12/20/05 11:18
There is nothing that stop you from doing this now. Just have the trigger write to a table and have
the app polling the table, reading off of it and removing the rows that has been handled. But, I
think you should look into Service Broker as it provide you with so much infrastructure code. At
least grab a book and read about SB (or play with it), so you can make the right decision. I
wouldn't be surprised if you in the end decide to wait until 2005 is implemented to cut down on the
dev time for this (thanks to Service Broker).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Laurence Breeze" <i.l.breeze@open.ac.uk> wrote in message news:43A7CA1D.6060804@open.ac.uk...
> Thanks Tibor,
>
> We currently run SQL Server 2000 but will upgrade to 2005 in time. If there's no way to do this
> in 2000 I'll have to wait a bit.
>
> Thanks Again.
>
> Laurence
>
>
> Tibor Karaszi wrote:
>> You can get all the queuing infrastructure for free. SQL Server 2005 includes a functionality
>> called "Service Broker", where your trigger does SEND to write to the queue and the service uses
>> RECEIVE to read off of the queue.
>>
>
Navigation:
[Reply to this message]
|