StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POASP.NET Custom Membership Provider for very large application
primarykey
Id
4175266
data
AcceptedAnswerId
4176372
AnswerCount
3
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2010-11-13T23:25:22.400
FavoriteCount
8
LastActivityDate
2010-11-17T20:19:27.970
LastEditDate
2010-11-17T20:19:27.970
LastEditorUserId
333255
OwnerUserId
333255
ParentId
0
PostTypeId
1
Score
9
ViewCount
2596
LastEditorDisplayName
text
Body
I have to come up with a membership solution for a very large website. The site will be built using ASP.NET MVC 2 and a MS SQL2008 database. The current Membership provider seems like a BIG overkill, there's way too much functionality. All I want to store is email/password and basic profile information such as First/LastName, Phone number. I will only ever need 2 roles, administrators & users. What are your recommendations on this type of scenario, considering there might be millions of users registered? What does StackOverflow use? I've used the existing Membership API a lot in the past and have extended it to store additional information etc. But there's tables such as <pre><code>aspnet_Applications aspnet_Paths aspnet_SchemaVersions aspnet_WebEvent_Events aspnet_PersonalizationAllUsers aspnet_PersonalizationPerUser </code></pre> which are extremely redundant and I've never found use for. Edit Just to clarify a few other redundancies after @drachenstern's answer, there are also extra columns which I have no use for in the Membership/Users table, but which would add to the payload of each select/insert statements. <ol> <li>MobilePIN</li> <li>PasswordQuestion/PasswordAnswer (I'll do email based password recovery)</li> <li>IsApproved (user will always be approved)</li> <li>Comment</li> <li>MobileAlias</li> <li>Username/LoweredUsername (or Email/LoweredEmail) [email IS the username so only need 1 of these]</li> </ol> Furthermore, I've heard that GUID's aren't all that fast, and would prefer to have integers instead (like Facebook does) which would also be publicly exposed. How do I go about creating my own Membership Provider, re-using some of the Membership APIs (validation, password encryption, login cookie, etc) but only with tables that meet my requirements? Links to articles and existing implementations are most welcome, my Google searches have returned some very basic examples. Thanks in advance Marko
Tags
<c#><sql><asp.net-mvc><login><asp.net-membership>
Title
ASP.NET Custom Membership Provider for very large application
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMarko
UserOwnerUserId
1. USMarko
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.