02-09-06 07:54 AM
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...
> In Oracle and I believe in SQL server you can setup what is known as a
> "link" or virtual table that is actually stored in another database.
>
> So the table MY_TABLE is in the Oracle database but the same table name
> is in SQL server and virtually refers to my Oracle table. When I issue
> "SELECT * FROM MY_TABLE", it actually queries the data from oracle but
> to the end program, it looks like a SQL server table.
>
> make sense?
>
[ Post a follow-up to this message ]
|