Kbase P168547: Until which number of users a user administration works properly?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/22/2010 |
|
Status: Unverified
GOAL:
Until which number of users a user administration works properly?
GOAL:
What you need to know as well if you have a large number of users?
GOAL:
Which database limits are limiting the numbers of users you can administrate?
FACT(s) (Environment):
OpenEdge 10.x
All Supported Operating Systems
FIX:
Since the data associated with "can" permissions is stored in the _file and _field record itself and there is a 32,000 byte limit on the size of any record stored in the database, that would indicate that there is a limit on the # of (or really size of) userids that can be added there. Wild cards are supported as part of the "can" permissions entries which can greatly help out here. That means the number of user it's self is probably not really becoming a limitation, but more the number of records you can have in the database, the size of the records etc. as documented within the available documentation.
If you make these permissions strings long and complicated, performance can be an issue because parsing the permission strings will take longer.
When you cache the db schema, we cache the character version of the CAN fields for each _file. When you setuserid we convert those permissions to "canflags" which are instant to look at. So we are not constantly looking at the character fields. Also, we "on demand" cache field information and we set flags in the same way there.