Re: Orchestration takes a long time after getting instantiated
by Jan Eliasen <eliasen@[EMAIL PROTECTED]
>
Jul 6, 2007 at 10:52 PM
On Fri, 06 Jul 2007 17:36:47 -0000, Sree <sreejonn@[EMAIL PROTECTED]
> wrote:
>This process does a query against a database as the first step.. The
>response is fast on some messages, slow on some. I want to make it so
>that the orchestrations as they get initialized get started with the
>process and query the DB. Any thing that waits on DB may wait but
>messages that can get the reply sooner should not have to wait for its
>turn till BTS picks it up....
I am not sure what you mean.Are you saying that the first thing that
happens in your orchestration is you query a database for some data?
>Is there a property I can set to start
>more orchestrations so that the ones that get delayed will wait and
>ones that are faster can go ahead...
There are some tuning options available. Take a look at
http://msdn2.microsoft.com/en-us/library/aa577523.aspx
--
eliasen, representing himself and not the company he works for.
Private blog: http://blog.eliasen.dk
Private email: jan@[EMAIL PROTECTED]