storing personalized information, what is best practice?

[Jeff]

Hey

asp.net 2.0

at work we are about to start on a new project. Creating a website. My
mananger has created the database. The database has a table holding user
information (not that standard ASP.NET membership table). This table holds
fields like, email, private email, contact, contact email. etc...
I know that this information also can be stored in the Membership tables as
well, think the table is named ASPNET_User or ASPNET_Profile? For the
Membership tables we can customize it's content using web.config (specify in
web.config the extra fields we wants)

I'm not sure what is best practice here. Stick with a traditional table or
using the Membership tables instead.

Any thoughts around this? any pitfalls I can encouter or functionality I
will miss by sticking to a traditonal table instead of using the Membership
tables?

My manager wants me to provide him with feedback on the database design, so
that's why I'm thinking about this scenario

Have a good day

 

[Michael Nemtsev [MVP]]

Hello Jeff,

Did your consider to use profile services?!
1) http://www.odetocode.com/articles/440.aspx
2) http://www.asp.net/AJAX/documentation/live/Tutorials/UsingProfileInformationTutorial.aspx

---
WBR,
Michael Nemtsev [Microsoft MVP] :: blog: http://spaces.live.com/laflour
:: http://twitter.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


J> Hey
J>
J> asp.net 2.0
J>
J> at work we are about to start on a new project. Creating a website.
J> My
J> mananger has created the database. The database has a table holding
J> user
J> information (not that standard ASP.NET membership table). This table
J> holds
J> fields like, email, private email, contact, contact email. etc...
J> I know that this information also can be stored in the Membership
J> tables as
J> well, think the table is named ASPNET_User or ASPNET_Profile? For the
J> Membership tables we can customize it's content using web.config
J> (specify in
J> web.config the extra fields we wants)
J> I'm not sure what is best practice here. Stick with a traditional
J> table or using the Membership tables instead.
J>
J> Any thoughts around this? any pitfalls I can encouter or
J> functionality I will miss by sticking to a traditonal table instead
J> of using the Membership tables?
J>
J> My manager wants me to provide him with feedback on the database
J> design, so that's why I'm thinking about this scenario
J>
J> Have a good day
J>