Not possible - by definition the trigger is firing as part of the transaction that caused the trigger to run in the first place and the trigger can only roll that transaction back, it cannot commit it. Think about it - what if the action that caused the trigger to run was one of a number of inserts, or updates, that were supposed to be part of the transaction, the trigger would then end the transaction before the others had happened.
Rather create a stored proc that performs your current action and then runs the proc that you're now calling from inside the trigger (probably after ending the transaction first).
after trigger is meant that it runs after the insert. It's still part of that transaction. It's not async. one option is do put the rows that have to be processed in another table in your trigger and then have a scheduled job do the thing you want to do in the trigger now.
If you provide more accurate info on what exactly and why do you want to do, you're more likely to get a better answer.
quote:I was thinking maybe using the trigger and the cmd_shell command to execute a batch file with the script in it!!
From what I remember of xp_cmdshell the calling procedure doesn't finish until the batch file/program completes which would probably add to your timeout issue.
What about writing the stored procedure parameter data to a table and having a scheduled job (run at an appropriate interval) that processes the rows since it last ran calling the triggered sp for each row. That way the event isn't dependant on the Insert at all.