I'm planning to apply Role Management feature to my new web site but I
have some doubts which I thought you can help.
The membership/role management system works like a charm on development
system, on a single machine that has both VS.Net 2005 and Sql Express
2005 version installed. But the main problem is, I'll host my site on a
shared hosting system. Here comes the questions...
1. If I choose to keep users database in ASPNETDB in App_Data folder;
a. I think this db works on SQL Express version that I
installed to my machine. If so, the hosting system will need a Sql
Server to be installed on the server which IIS runs. This may be
impossible for my hosting company.
b. If this database runs on a seperate instance and can be
used without a separate Sql Server installation, most probably it's a
Sql Express version which may be weak for larger sites.
c. Most of the applications use the other data tables joined
to Users tables to show the data with the User Name instead of User ID.
So, if this is the way to go, should I put the other tables in this
ASPNETDB database?
2. If I choose to keep users database on the Sql Server that I
installed;
a. I tried this method and I realized that she system holds
the user data in a centralized way, one table for all the websites with
their ApplicationID to differ. In a shared hosting system, this is not
possible for lots of reasons as you may realize.
What I really need is, keeping the user system in my "seperate" Sql
database neither in App_Data forder, nor a shared user table. IS there a
way to accomplish this or should I go into the "old ways"?
Thanks in advance
Serdar KALAYCI
