General discussion

Locked

Common or separate database when online

By shobhak ·
We are developing web extensions for an existing client - server enterprise solution. The main enterprise data resides in Oracle. This data has to be protected as it involves privacy issues. The web extensions however require the data to be current at all times.
If we want to maintain 2 separate databases ( one for online and one for the client - server access) - what methods can we use to synchronise them? Secondly, what security steps can we take in case we decide to use a single database for both applications?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Common or separate database when online

You have quite a task ahead of you! You're trying to combine the OLTP (OnLine Transaction Processing) with old, big-iron batch processing. To do this, you'll need to use MTS (Microsoft Transaction Server) or some other kind of programmable middle tier.

I would write an MTS package that retrieves data from the local database, and periodically updates the Oracle server with the local data. If the update is successful, a bit is set in the local database record to indicate that it is synchronized with the Big Iron.

Collapse -

Common or separate database when online

by shobhak In reply to Common or separate databa ...

The question was auto-closed by TechRepublic

Collapse -

Common or separate database when online

by Albert Franco II In reply to Common or separate databa ...

If the clients must have current data at all times then local databases are not an option. Local databases will make it impossible to assure that all clients are working with the same data. Of course, this problem will be more or less important depending on how much of the database is actually stored locally. (Think about DNS servers, it takes up to 24 hours for syncronization to occur across the internet!!)

If you store say 250 whole copies on clients then the delay between getting all of the copies can be significant and depending on the use of the data may cause unsolvable conflicts.

If the data is essentially read only it doesn't much matter, but the more the clients edit the data the more prominent and frequent the sync errorswill be.

Security should, actually, be tighter if the data is only on the server. There, only authorized accesses are allowed and sensitive data can be reserved or masked depending on wether or not the client must edit it. A good middle tier program can be the only authorized access to the Data and the middle tier would not have access to the most sensitve stuff that a client should have.

Individual dbs also present a risk of unauthorized copying. It's harder to protect 250 clients than one server...

for more details: apf2@apf2.com

Collapse -

Common or separate database when online

by Albert Franco II In reply to Common or separate databa ...

In the next to the last paragraph, the last line should end: stuff that a client should NOT have.

Collapse -

Common or separate database when online

by shobhak In reply to Common or separate databa ...

The question was auto-closed by TechRepublic

Collapse -

Common or separate database when online

by shobhak In reply to Common or separate databa ...

This question was auto closed due to inactivity

Back to IT Employment Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums