Membership and Role Management
The books I have read, (beginning asp.net 2 and professional asp.net 2) only give examples of using the supplied aspnet_membership, aspnet_users, etc.. tables for taking care of authorization, profiles and membership management.
I am upgrading a classic asp application to dotnet and all of our authorization is keyed off of the users table.
My questions are:
From anyones real world experience, should I take the trouble to migrate all of our users (including staff and managers) information and roles into the special dotnet sql database used for membership and role management?
Is this going to cause problems running queries that will need to pull joins between our database and the special dotnet database?
Or should I keep our current tables and relate them on a one to one basis with the dotnet sql database?