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?