SYMPTOMS
This article covers general database/table infrastructure including the record association between tables.
CAUSE
Not applicable.
RESOLUTION
DBO.Principal is the table a user or group is imported into and assigned a unique ID number
DBO.Permission (This table associates a role ID with a certain permission or access type.)
DBO.PermissionInfo (This assigns an ID number to a particular capability in the application that can then be assigned to a role and in turn be assigned to a user or group.).
The three below tables are what contains the association between an imported user and the role they are assigned to:
- When generating a new Role (nobody assigned), that role is created in the DBO.ROLE table.
- When you import a user, they are then listed and assigned an ID number in the DBO.PRINCIPAL table.
- The user is then associated to the role using that assigned ID number and the Role ID number from the Role table in a table called DBO.PrincipalRole.
- Since each user could have access to any number of roles, there could be quite a bit of records in the PrincipalRole table. One for each user and the role they are assigned to. So for example, if you were imported into the system and assigned an ID of the number 1 and were assigned to role ID 1, 2, and 3 there would be 3 total records for your ID of number 1
APPLIES TO
3.7; 3.7 SP1; 3.7 SP2; 3.8
Comments
0 comments
Article is closed for comments.