We have an application that manages security at the application level. To facilitate this we have created an Admin Tool that manages users and security. In 2000 if we removed a user from the database and then dropped the login. if that user was a member of another database it would throw an error and we would capture this and report it to the Administrator that the user was dropped from the database but the login could not be dropped.
In 2005, it just drops the login (using both the Drop Login command and the sp_droplogin). This can create orphane users in other databases in the same instance. Is there a way to avoid this?
Thanks in advance for any help