Membership Provider users in different tables

I have an existing database with users and admin开发者_开发问答istrators in different tables. I am rewriting an existing website in ASP.net and need to decide - should I merge the two tables into one users table and just have one provider, OR leave the tables separated and have two different providers.

Administrators, they need the ability to create, edit and delete users. I am thinking that the membership/profile provider way of editing users (i.e.

System.Web.Profile.ProfileBase pro = System.Web.Profile.ProfileBase.Create("User1");
pro.Initialize("User1", true);
txtEmail.Text = pro["SecondaryEmail"].ToString();

is the best way to edit users because the provider handles it? You cannot use this if you have two separate providers? (because they are both looking at different tables).

Or should I make a whole lot of methods to edit the users for the administrators?

UPDATE:

Making a custom membership provider look at both tables is fine, but then what about the profile provider? The profile provider GetPropertyValues and SetPropertyValues would be going on the same set of properties for users and admins.

Probably you should merge the two tables into one and use a RoleProvider to make the distinction between administrators and "normal" users.

Alternatively, you could implement your own, custom membership provider, which would use both tables.

Mike, My advice is to go ahead and merge your two 'membership' tables and segregate admins from non with roles.

(This is, I know a duplicate of the previous answer but I feel the need to explain..)

In this way, unless you have some compelling reason to implement custom providers, you will be able to leverage the stock providers and database structure to provide a robust user management story for your website without writing any code (that you have to test and maintain).

.2 pesos....