how can a trigger act asynchronously to the event that fired it in sql server 2005?

if service broker is not an option, how can the trigger and sp(s) called by our trigger act asynchronously to the event that fired the trigger in the first place. We are more concerned with the original event being committed than the actions that follow via the trigger.

Having the trigger call a job using sp_start_job would be one option if you don't want to use Service Broker, although Service broker would be a better approach.

-Sue

|||are jobs supported in all editions (including express)? I thought i read something once saying they (might have just been scheduling) are not supported in express.|||

You could also have the trigger just insert a request into a 'queue' of your own and have a SP that periodically wakes up and processes any pending requests. SSB and SQL Agent help this scenario by providing queues and jobs, respectively, but you could build some of this yourself (using WaitFor, etc.).

Don

|||

so service broker does come free and full featured (except for inter instance) with express? how about the sql job feature, except for maybe scheduling?