Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
robertc
Starting Member
7 Posts |
 Posted - 2007-09-26 : 18:40:01
|
| Hi,I'm currently building a database that is going to have at least 6 different types of users accessing it via a web application.A user will have different information collected about them. A few of of the users will have the same or similiar information collected about them.I will be using role based authentication. Now my query is this;Scenario 1:Would it be a good idea to keep all the users common information in one table. Ie. thier username,email,password,name. Then create a tblDetails for each type of user that would contain the different data. That way i can just check one table to verify thier login credentials.ORScenario 2:Would it be best to create a seperate table for each type of user and then log them in based on the credentials stored in each type of users respective table.Hope this is clear. I'm leaning towards scenario 1, although I've used scenario 2 before. Just wondering which would be preferred.CheersRobC |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-09-26 : 18:48:03
|
| I would have a common table and then separate detail tables for the different types. I doubt that there is a best practice on this, just preferences.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
robertc
Starting Member
7 Posts |
Posted - 2007-09-26 : 19:18:57
|
| Thanks for your input Tara.I've decided to go with scenario 1. |
|
|
|
|
|
|
Best Practice For Database Design Scenario