Help on Biztalk Solution Desing

[steve...@googlemail.com]

Hi,

I have been asked to create a biztalk solution which copies new
records (insert/update delete) from one database to other.

Reason is currently there are lots of tables in 1 single database. few
of them are used by sales team and rest are used for administration
purpose. Now they want to separate these databases and replace the
whole application with different-different in house applications. But
want to keep both the databases in sync for time being(I guess they
are using biztalk as mediator because in future if they want to
implement some routing rule they can implement )

Can some one suggest me good solution design for such scenario?

Below is something what I'm thinking right now....

Create triggers on existing tables so whenever records are modified
they are also inserted in appropriate dummy tables.

Create front facing orchestration which will poll to main table and
publish records to destination DB or whatever it will be (for example
I have 2 tables customer and customer profil, Where 1 customer can
have multiple profiles. So when ever customer is modified it will make
entry in dummy customer table and when ever profile is modified it
will make entry in dummy profile & dummy customer table. Now my front
facing orchestration will poll dummy customer information. When record
is found it will process the message and other orchestration will get
all the profile information and create a final message with customer
and all profile info. And it will be updated to destination DB or what
ever it will be.)

Problem here is I'm thinking with very narrow set of table schemas
where actual database has 50+ tables so I'm not sure I can manage the
relation ship between all the tables and I can cover all the tables
with this kind of logic (don't have any issue if I have to create
multiple front facing orchestrations to cover all the tables).

Also I don't like to have trigger for each table and generate dummy
tables for those. (Note: I can't alter existing database schema so I'm
creating dummy tables through triggers and also will create jobs to
clear the processed records from DB to clear processed records).

Please let me know your thoughts on this design or any other efficient
alternative which you can think of.

[m...@privacy.net]

a good life by their
morals, miracles by destroying either their truth or the conclusions to be
drawn from them.

If we believe them, the Church will have nothing to do with perpetuity,
holiness, and miracles. The heretics deny them, or deny the conclusions to
be drawn from them; they do the same. But one would need to have no
sincerity in order to deny them, or again to lose one's senses in order to
deny the conclusions to be drawn from them.

Nobody has ever suffered martyrdom for the miracles which he says he has
seen; for the folly of men goes perhaps to the length of martyrdom, for
those which the Turks believe by tradition, but not for those which they
have seen.

845. The heretics have always attacked these three marks, which they have
not.

846. First objection: "An angel from heaven. We must not judge of truth by
miracles, but of miracles by truth. Therefore the miracles are useless.

Now they are of use, and they must not be in opposition to the truth.
Therefore what Father Lingende has said that "God will not permit that a
miracle may lead into error..."

When there shall be a controversy in the same Church, miracle will decide.

Second objection: "But Antichrist will do miracles."

The magicians of Pharaoh did not entice to error. Thus we cannot say to
Jesus respecting Antichrist, "You have led me into error." For Antichrist
will do them against Jesus Christ, and so they cannot lead into error.
Either God will not permit false miracles, or He will procure greater.

Jesus Christ has existed since the beginning of the world: this is more
impressive than all the miracles of Antichrist.

If in the