I was reading through this post here MisfitGeek: Adding ASP.NET Membership to your OWN Database.
and thought to my self what the common practice is. What do developers using ASP.NET membership and authorization in their applications recommend as a best practice? Creating the membership tables in the same database that stores their applications data or configuring a second database to store ONLY the membership information?
My current setup is a different database for membership information ONLY but am thinking that increases the number of databases I have to maintain. If I have 5 applications using ASP.NET membership, then that means 5 more ASP.NET membership databases.
So do you normally create the ASP.NET membership tables in your main database or you configure a separate membership table?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
I personally just added the asp.net membership stuff to my own database. I then wrote a basic wrapper class around System.Web.Security.Membership class so that the code acts like its using its own membership stuff. Its pretty slick and not that hard to do. If you need assistance setting it up, here is what I did.
The link you provided on how to set it up is waaaaaaaaaayy more complicated that what I used:
- Run C:WindowsMicrosoft.NETFrameworkv4.0.30319aspnet_regsql.exe.
- Hit Next.
- Select “Configure SQL Server for application services…” and hit Next.
- Select “Windows Authentication” and the “XXXX” Database and hit Next.
- Your settings are then presented…then hit Next.
- Finally you should be presented with a done screen, hit Finish.
I have screenshots in the doc if you really need the walkthrough.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0