Feb 02, 2015 05:22 PM|johnjohn123123|LINK
I am a bit intrigued by your requirement. Do you really need to duplicate all the data that is already maintained by the active directory? Wouldn't it be sufficient if you implemented windows authentication in your application and then made use of it to track
who was making changes to your assets? Maybe if you could share more information about what the end goals of your application are, we would be happy to help you design your system better.
i will not be duplicating the whole info , i will be retrieving the following info :-
1. first name, last name, email address, sam account name + telephone number. and still these info will be managed by the AD,, but having these info inside my own table will ease sorting , searching the info.
2. now i am using windows authentication for log-in users, but we want to have our own tables for managing the security roles.
now the problem i am facing is that if a user leave the company we remove him from the AD, but i can not remove him from my users table since he might have created assets inside the system ,, and i can not delete the user if he is being referenced by a FK
from another table,, so my question is how usually enterprise systems manages these scenarios ... so if a parent record (in my case the users table records) is no more active (leave the company) how i can remove him from the table without causing a referential
integrity exception to be raised if there are child records referencing it ...