Hi.

I don't really have a problem per se but since I am not a 24/7 DB
developer I'd appreciate an experienced set of eyes to provide some
feedback (and help me avoid future problems).

I am getting under way with designing a new MS SQL DB architecture
that uses the ASPNETDB for membership, profiling, and roles.

I am new to the ASPNETDB and, after some experimenting, decided to
extend the profiling features so I could more clearly
identify my custom data. An example of the schema is here:

<a href="http://s103.photobucket.com/albums/m156/pbd22/?
action=view&current=schema.jpg" target="_blank"><img src="http://
i103.photobucket.com/albums/m156/pbd22/schema.jpg" border="0"
alt="Photobucket"></a>

The "problem" is that I am finding myself dump all my custom data in
the ProfileData table and wonder if this is going to cause problems
down the road.

Could somebody take a look at what I have thus far and advise as to
what other tables would be wise to include at this point (assuming
generic features of a social networking web site that allows users to
establish an account, create a profile, add / remove friends, add /
remove applications, and so on... ). Maybe some of the columns I have
in ProfileData should be in separate tables? Also, any other design
advice based on what I already have is also welcome.

Thanks, much appreciated.

On Feb 23, 4:21*pm, pbd22 <dush... (AT) gmail (DOT) com> wrote:

My link really didn't go as planned... try this:

http://s103.photobucket.com/albums/m...ent=schema.jpg

or this:

http://i103.photobucket.com/albums/m...d22/schema.jpg

Thanks again.