Hi everyone,
I need a quick ‘is this okay?’ check. I have a user whose last name was spelled incorrectly when he was created in the security module. I know changing the userid is bad for all sorts of reasons, but is there a problem if I want to just change the last name?
Cheers,
Kathleen
So, bottom line, is there a way to - for instance - create a new login for a person who's name has changed, but still have access to that person's old login's records? Some sort of TX table that links them together? As a database guy my instinctive reaction to that is "what are you nuts? it's just a login, who cares if your actual name has changed?" But I guess I have to ask. Due diligence and all that sort of rot.
Thanks!
Matt Gonzales said:create a new login for a person who's name has changed, but still have access to that person's old login's records?
No, a new login would be a new login, completely separate from the old one.
Re: changing names on existing Tessitura logins, we've historically avoided this as above, but recently was persuaded to try this in one case. I believe I did this by updating the login name and lname in the Security app, deleting the SQL login via SSMS, then dropping/(re)creating the login back in the Security app. Finally, the user had to reset their password, then all was well.
What about all the objects and history in Tessitura marked with the old userid?
Gawain Lavers said:What about all the objects and history in Tessitura marked with the old userid?
Re: history, we left it as-is. They could be updated, but e.g. we have rows of data converted from our pre-Tessitura system left with the last-updated-by values they had when we imported them, including in some cases long ago departed users that have never existed in Tessitura.