November 3, 2009 at 9:44 am
We recently discovered that when an employee’s name changes and we update their username/login appropriately that interesting things occur with Reporting Services.
I’ve notice that when this occurs, all access visible through the Report Manager is updated automatic to reflect the new username. However, in the users table the username is still the old one. So I’m assuming they still have access because the SID did not change. Does that sound right?
This is a bit of a problem when we query for access for an employee in this scenario. It is preferred to query by Employee Id (different than the username/login) but we use the username to join on. Thus you see the dilemma, as the rows with the old username will not join as we do not store/keep the Employee detail for the old username.
Has anyone encountered this before? Any suggestions of a resolution?
I was possibly thinking that we could remove the “old” username record from the Users table and then add the “new” username back to the appropriate folders for access. Good Idea? Or maybe just change the username field to reflect the “new” username?
I thank you in advance for any feedback you may provide.
Much appreciated
February 23, 2010 at 9:25 pm
The SID is the key, you're correct. I experienced this when we changed domains. For a usage report, I wonder if you can query AD with the SID that links to the new user name and back to your employee reference table...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply