I have several clients, and some of them have several projects. I usually create the membership and role tables in each project's database. This means that if I have 10 projects, I would have 10 membership/roles databases. From the point of view of how useful that is, for me it works good, I wouldn't like to create one master membership database and then have every different app use it as a Master Authentication table. But my question is, if I have several of those membership/roles sets, is it going to be harder on the SQL Server to deal with all of them?
What is the best recommended way to do it?
...
Go to the complete details ...