The issue was resolved: the two IDs were not identical!!!

The new ID doesn't have the VIEW ANY DATABASE privilege which the DBA said By default, the VIEW ANY DATABASE permission...

Thank you very much for your advise, I will have to talk to my colleague tomorrow as he already left.

I guess delete/re-add would work.

I still don't get the point here.

I had a colleague with privilege and ran the sp_change_users_login, apparently some parameters must apply.

I had him ran sp_helplogin id and both IDs return...

Thanks for reply.

I do not have both the IDs, I will only use the new one and it's domain ID, meaning I don't have password for it.

By the way: we have to apply least privilege to the id, it would be troublesome to give more privilege to the id, currently it is data reader, and like...

Thanks for replies, I actually found a way to use stored procedure which is much easier for me, especially on this case.

Thanks guys, I was thinking it too complex. :w00t:

I didn't use command, I was using SSMS, forget it, never mind.

never back it up, don't understand why it prevented me

as it is a very new and still under development database, I rebuild the db without back up the old one.

Thank you for your reply

Thanks David and Richard, advise gladly taken.

Richard Warr (12/4/2013)

---

I'd go for the redesign as well. It's not a major one.

Take out the Workflow field from the Project table and have another table called ProjectWorkflow which would...

Thanks for the clarification

Ed Wagner (11/8/2013)

---

Yes, it should revert back to your original username. This may sound like a long shot, but did you actually execute the REVERT? If you're running...

The cause turns out to be...