Re: How to design the database

The advice the prior writers have given is nothing I could argue with. It would be pointless overcomplication to create three instances (databases sorta kinda but people can argue the point of the difference between those two terms until the moon turns blue) to mirror what you have in SQL Server. Oracle Applications is structured that way, with separate users (as the others have called schemas, which can be confusing to someone new to Oracle; I prefer to think of Oracle as a collection of different users that own different things and have differing privileges; schema always implies to me a set of objects), but anyway... OA has users like PO (Purchasing), AR (Accounts Receivable), and so forth; so if Oracle Corporation arranges things that way, you could do far worse than by following their example.

Having said that, I'll contradict myself a bit. I have found that some applications, particularly those written for multiple RDBMS instead of just Oracle, may take the easy way out and insist on DBA privileges, or logging on as SYSTEM into Oracle (even worse) or even directly fiddling with Oracle's core, base tables like the data dictionary (truly the ultimate horrible).

Depending on your app, you may wish to consider having them in separate instances if they want to make use of privileges such as that.; better still of course, is not to use apps that do things like that.

Packaged 3rd party software seems to be the worst offender in wanting things that you would not want to grant to an application.

For whatever it's worth.

RSH.
"Rudy Susanto" <rsusanto_at_atlas-sp.com> wrote in message news:1a928d0b.0203242220.46c4ce1c_at_posting.google.com...
> Hi all,
>
> I just have a little problem about database design with oracle
> database.
>
> I have 3 databases on sqlserver such as gldt(general ledger),
> fadt(fixed assets), and leasedt (leasing). I want to create database
> on oracle but i don't know what i sould do because the oracle and the
> sqlserver is not the same.
>
> Maybe i just have 2 choices, create 3 databases just like on sqlserver
> or just create only one database. If i create just one database, maybe
> too difficult to me to maintain the database. When i create 3
> databases, i will have 3 instances that will degrade the performance.
>
> I don't know which is better, i need some suggestions.
>
> Thank in advance,
> Rudy Susanto
Received on Mon Mar 25 2002 - 11:01:26 CST