We have an application where our customers each have their own database,
and their own username/password that grants them access to that database.
This is on postgresql.
We are considering one of two approaches with sapdb. One is to create a
separate set of tables for each user (about 20), and log in the users from
our application using their database username/password.
The other approach we could take is to have one set of tables under a
master user, add another column to each table that contains the customer
id, and do the login authentication in our application using our own
authentication database.
Approach number two does make it easier to update schemas when we need to
make a change, and makes management easier. All the data is transaction
based. These are financial transactions so separation is also an issue.
One thing I do not like about approach two is that it leaves open the
option for bugs in the application which could let users see other users
data.
My main question for the list though is performance related. Does a large
number of users in the system degrade performance significantly for the
login process? And how much extra overhead is it when you have say 5000
users each with their own set of tables versus just one set of tables
under a single user? Will query performance degrade significantly with
the large number of users who each have their own tables?
Chris
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
