It really depends on how you define "real-time"? Pull access from a source
database into BizTalk is done through polling (via a receive adapter), as
mentioned earlier in this thread. How often do you have to poll for changes
in order to maintain real-time data - and if you're polling too often, how
much strain does that put on the database?

BizTalk isn't ideal for this kind of situation.

Hugo

http://hugo.rodger-brown.com

"RedHair" wrote:

> For security issue, the front-end and back-end db should not have direct
> connection.
> (1) if hacker attack front-end system successfully, then Oracle is in
>      danger and without any back-up system.
>
> For performance and stability issue, the front-end and back-end db should 
be
> totally separate.
> (1) if the network connection (between SQL and Oracle) is broken
>      then the front-end system can not work
> (2) if hacker use DOS attack to occupy resource of Oracle db, then
>      both front-end and back-end system can not work
> (3) if back-end Oracle db is out of order no matter due to H/W or S/W
>      then front-end system can not work too.
> (4) The table schema are not same between two db, the Oracle schema
>      is designed for back-end system and isn't normalized and optimized
>      to front-end system. Front-end system query back-end db will cause
>      performance issue in long term.
>
> Our goal is to have these two systems work independently and be each
> other's back-up system, not allow two systems crash at same time.
> Currently, I use MSMQ to do two ways data sync, but want to migrate
> to BizTalk.
>
> Thanks
>
>
> "CranCran77" <crancran@gmail.com>
> ???????:1139468340.857349.219160@o13g2000cwo.googlegroups.com... 
>
>
>

[ Post a follow-up to this message ]