Minimal database for ASP.NET MVC 3 user management / membership -

i new asp.net mvc 3 , dealing database inherited me visual studio master. there lots of stored procedures , user roles aspnet_membership_basicaccess, aspnet_membership_fullaccess etc.

do need this?

i can remember other mvc solutions, ruby on rails's devise authentication plugin: needs one-two tables , 1 database access role - , still pretty secure.

what minimal database structure support asp.net mvc 3 user management?

the short answer yes, need this, because membership system relies on sprocs , roles.

the longer answer is, going using membership? if not, no. if you're going using membership, going using sqlmembershipprovider? if so, yes, need those. if you're going use universal providers instead, need different set tables , supporting configurations.

so without knowing anything you're doing, can is, if don't understand why it's there, don't mess it.

i fail understand why mention rails, it's totally different toolset , framework. it's complaining motorcycle needs gas , oil when bicycle doesn't (not i'm saying rails less powerful, saying it's different).

asp.net mvc doesn't do user management itself, include templates rely on default asp.net membership system. in visual studio 2010 uses sqlmembershipprovider default, in visual studio 2012 uses universal providers default mvc3, , simplemembership default in mvc4.

asp.net mvc doesn't know or care how user management, it's not part of framework. delegates via authorization filters, default merely @ asp.net iidentity , iprincipal.

if you're going user management, need decide on how you're going that. either roll (custom membership provider, custom iidentity , iprincpal provider, etc...), or use existing membership provider (there many, , microsoft has @ least half dozen different ones). or can choose go defaults, in case it's pretty in pretty bare minimum situation.