I am not sure if I fully understand your question.
In each instance of business process the query is called only once. So the
second call (= call in another instance of business process) will be
processed in the same way. Data can be modified by another type of
business
process which uses transactions. So result of the query is not necessarily
the same. Also as I wrote before, the query (where part of the query) is
built dynamicaly based on few parameters of the stored procedure.
"Paul Somers[MVP]" wrote:
> How do you manage the second call that would return the exact same
response
> if you are not modifying any data?
>
>
>
> "Ladislav Mrnka" <LadislavMrnka@[EMAIL PROTECTED]
> wrote in
message
> news:0EA13184-ADC9-4966-BB55-B5EB4DA102AD@[EMAIL PROTECTED]
> > Hi Paul,
> >
> > I actually don't need to modify data. My stored procedure only build
some
> > dynamic SQL Query and runs it. It returns single record (the
aggregate)
> > and I
> > used it in construction of complex response (data from other sources
are
> > used
> > in result transformation). I guess running query (no data
modification) in
> > distributed transaction is overhead.
> >
> > Best regards,
> > Ladislav
> >
> > "Paul Somers[MVP]" wrote:
> >
> >> You should be using the transaction, it didn't used to be there, this
was
> >> added post 2004.
> >>
> >> There are many what if senarios when accessing sql and touching sql
> >> database
> >> tables, that need the transaction if it goes wrong.
> >>
> >> It is always better to use a stored procedure, and do all of your
work in
> >> there for modifying the query.
> >>
> >> What is your requirement that you would like to NOT have the
transaction?
> >>
> >> Paul.
> >>
> >>
> >> "Ladislav Mrnka" <LadislavMrnka@[EMAIL PROTECTED]
> wrote in
> >> message
> >> news:61232872-1453-4EC8-820A-0AACDAF972B5@[EMAIL PROTECTED]
> >> > Hello,
> >> > is it possible to use parametrized query in SQL Receive ****t? I'm
using
> >> > two
> >> > way SQL Send ****t to call stored procedure but I don't like the
idea of
> >> > running simple SQL Selects in distributed transaction (SQL adapter
> >> > always
> >> > creates one when Send ****t is used) so I'm wondering if there is
any
> >> > workaround with Dynamic Receive ****t.
> >> >
> >> > Thanks in advance for response.
> >> >
> >> > Best regards,
> >> > Ladislav
> >>
> >>
> >>
>
>
>
|
