Hi Gurus,

To update database from orchestraion,

there are two ways, use sql adapter, or call a .net component,
going thru adapter requires, create schema, port binding
going thru .net component doesn't require above 2 steps and eases from
maintenance and doesn't introduce any new issues,
methods in component require static, if not serializable.

can somebody advise me on, is going thur .net component is a better choice ?
and is it that, when 10 orchestratins running, 10 .net components are
created in above scenario ?

TIA
Kishore

[ Post a follow-up to this message ]

We have used both .Net components and functionality built into BizTalk.
Reasons:
.Net
Had to call Stored Procs inside a map that was driven by a repeating node
in the data
BizTalk Orchestration
Error Handling built in
Ability to easily promote through different enviornments

I would recommend using functionality in BizTalk as much as possible, for
supportability.

"medhanush" <medhanush@discussions.microsoft.com> wrote in message
news:F3521ACA-1610-48B3-B351-1D47A4DB84E0@microsoft.com...
> Hi Gurus,
>
> To update database from orchestraion,
>
> there are two ways, use sql adapter, or call a .net component,
> going thru adapter requires, create schema, port binding
> going thru .net component doesn't require above 2 steps and eases from
> maintenance and doesn't introduce any new issues,
> methods in component require static, if not serializable.
>
> can somebody advise me on, is going thur .net component is a better choice
> ?
> and is it that, when 10 orchestratins running, 10 .net components are
> created in above scenario ?
>
> TIA
> Kishore
>
>
>

[ Post a follow-up to this message ]