I am planning to combine my membership/role database with my applications main database. I have successfully executed the SQL Server setup (aspnet_regsql.exe) to create the tables, views, etc. necessary for the main database to function for membership and roles.
First question: is combining the two databases as one recommended? It's not going to be a high traffic site.
Final question: if this is an acceptable design how do I copy over the data in the original membership/role provider database into the new tables in the main database?
...
Go to the complete details ...