Re: Different ways of setting up a multi user database.

I prefer to use synonyms to hide the name of the schema owner. This allows you to have more than one version of the schema loaded onto a single database. This can be useful in your "TEST" database, and also allows you to install the application on almost anyone's system. Just this summer we installed a small application (no names mentioned :^) that had a fixed schema, and wouldn't you know it, it was the same username as one of our clients! Try telling someone that you want to change their 5 yo userid!!!

Where possible, global, public synonyms are the easiest to manage. But you can create a script to create private synonyms very easily. It really varies depending on your goal. Designer/2000 uses private synonyms, allowing you to have multiple version of the CASE tool loaded on single system, very handy that!

Thor HW
George wrote in message <362AE3BB.6CAE_at_expohire.com.au>...
>I have created a database containing about 30 tables to be accessed by
>60 users. All the tables that are to be access by all users will be
>stored in one schema. The client will be a Visual Foxpro interface
>accessing the Oracle database through ODBC.
>Which is better:
> 1. Create synonyms for each table in the database in each user account,
>thus not requiring to include the schema name for every object
>referenced in the client code
>
> 2. Make all client code accessing the database include the schema name.
>(Thus not requiring the use of synonyms).
>
>I know this is a very open ended question however I just want some
>opinions on both the above methods relating to proper client-server
>design and security.
>
>I would welcome any other ideas/methods as well.
>
>Thanks in advance
>
>George.
Received on Mon Oct 19 1998 - 22:54:12 CDT