|
Home > Archive > BizTalk Server General > January 2005 > Biztalk with (SQL Notification Services or Triggers)
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]
| Author |
Biztalk with (SQL Notification Services or Triggers)
|
|
|
| We are working on designing an integration system so all data changes in our
SQL Server get sent over to other third party applications, for example when
the employee get entered to our app that employee record will need to be sent
to two other applications, there are two scenario’s we are considering
Design A:
Use SQL Triggers to keep track of data changes and notify Biztalk about it
and let biztalk handle the sending the message to other vendor apps
Design B:
Use SQL Notification Services to keep track of data changes and when a data
change occurs , notify biztalk and let biztalk handle the sending the message
to other vendor apps
Any suggestions as to which way is better pros and cons? Thanks,
| |
| Scott Woodgate \(MS\) 2005-01-28, 2:46 am |
| Why not use the SQL adapter?
"Kaz" <Kaz@discussions.microsoft.com> wrote in message
news:0A6E29D9-BCC5-455C-92B0-ADF9BE204D67@microsoft.com...
> We are working on designing an integration system so all data changes in
our
> SQL Server get sent over to other third party applications, for example
when
> the employee get entered to our app that employee record will need to be
sent
> to two other applications, there are two scenario's we are considering
> Design A:
> Use SQL Triggers to keep track of data changes and notify Biztalk about it
> and let biztalk handle the sending the message to other vendor apps
>
> Design B:
> Use SQL Notification Services to keep track of data changes and when a
data
> change occurs , notify biztalk and let biztalk handle the sending the
message
> to other vendor apps
>
> Any suggestions as to which way is better pros and cons? Thanks,
>
| |
|
| See the point is to how in real-time fashion send the changes to Biztalk...
How would SQL adapter can help you to know what changed... in my scnario A :
as soon as the data changes for that table the trigger will insert a record
in another table(lets call it SyncTable) that indicates the recordID and
tells you what changes and then SQL Adapter can know what changed by
querying the SyncTable periodically....
That's one approach and then I came across SQL Notification Services which
essentially does the same thing, do you have any experience with SQL
Notification Services and Biztalk?
Thanks,
-Kaz
"Scott Woodgate (MS)" wrote:
> Why not use the SQL adapter?
>
> "Kaz" <Kaz@discussions.microsoft.com> wrote in message
> news:0A6E29D9-BCC5-455C-92B0-ADF9BE204D67@microsoft.com...
> our
> when
> sent
> data
> message
>
>
>
|
|
|
|
|