|
Home > Archive > BizTalk Server > January 2005 > sql adapter
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Can I always call a .net assembly to do my database stuff instead of using
SQL adapter?
Thanks
| |
| Alan Smith 2005-01-25, 7:48 am |
| Hi,
You can call a .net assembly instead of using the SQL adapter, I create a
DAL class using static methods for this, as you don't have to worry about
serialisation/atomic scopes in the orchestration.
Adapters are good for using when you have a system boundry, as they provide
relyability with the retry settings. When connecting to a local database, you
can use a .net data access layer, you will gain a lot in performace this way,
as you are not going through the message box.
Regards,
Alan
"mp" wrote:
> Can I always call a .net assembly to do my database stuff instead of using
> SQL adapter?
>
>
> Thanks
>
>
>
| |
|
| Hi Alan,
Thanks for your reply.
Why did you use static methods for this?
Thanks
"Alan Smith" <AlanSmith@discussions.microsoft.com> wrote in message
news:82F3F9FC-7A8B-4D0A-A700-4AB3FC62224C@microsoft.com...
> Hi,
>
> You can call a .net assembly instead of using the SQL adapter, I create a
> DAL class using static methods for this, as you don't have to worry about
> serialisation/atomic scopes in the orchestration.
>
> Adapters are good for using when you have a system boundry, as they
provide
> relyability with the retry settings. When connecting to a local database,
you
> can use a .net data access layer, you will gain a lot in performace this
way,[vbcol=seagreen]
> as you are not going through the message box.
>
> Regards,
>
> Alan
>
>
> "mp" wrote:
>
using[vbcol=seagreen]
|
|
|
|
|