If you need to run the SP at interval through-out the day and start an
orchestration each time, then I agree with McGeeky.  This would be a one-way
receive port.  Receive locations have polling intervals such as every 30
minutes or every 3 hours.

But just to add - you can call a stored procedure from an orchestration.
This would be a request/response send port.  So for instance, if something
else triggered your orchestration to run, and then you need to call the
stored proc, this could work too.

If you need precise control of when the stored proc runs, you could use SQL
agent to schedule a second stored procedure that writes a row to some table
that acts as a trigger mechanism. You could have a receive location that
polls this table every few minutes, and when it finds a new row, it could
start an orchestration that then calls your first stored proc.

Neal Walters
http://Biztalk-Training.com



"McGeeky" wrote:

> You can set a stored procedure to be run at regular intervals using a SQL
> receive port. The result set returned from the stored procedure is convert
ed
> in to a message.
>
> --
> McGeeky
> http://mcgeeky.blogspot.com
>
>
> "Eric" <ericstott.dontspamme@hotmail.com> wrote in message
> news:%23Y8AjLEeFHA.2732@TK2MSFTNGP14.phx.gbl... 
>
>
>

[ Post a follow-up to this message ]