We have a situation where somebody will need to change a username on our intranet, most often due to marriage.  So they may be jSomebody@somewhere.com (username jSomebody) and then get married... now they are jNobody@somewhere.com and their username would change to jNobody.  I have been just going into the database and changing the appropriate fields in the aspnet_Membership (email), Users (username and email), and aspnet_Users (username) and that seems to be doing the job.

Question is, would that be considered the "correct" way to do it (maybe write a stored proc to facilitate the process), or is there already something in code that can perform this task?  Am I dorking up my database by doing this at all?