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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-02-08 : 11:13:35
|
Eugene writes "This question arose from the follow scenario:
I'm building one of those basic login/password scripts where the database contains a table called 'Users' with LoginID as the primary key and the other column being Password. The ASP script will check the username and password against the database and either let the person in or cut off one off their fingers and ask them to try again. Nothing special.
The thing is that I also need to store some extra information about the user which unlike the login script, will be used very rarely. So the question is: Do I put the extra information in a separate table and join the two on LoginID on the rare occasion that I need the extra info or can I add more columns to the 'Users' table without affecting the speed of my login script.
Let me add that I'm not JUST too lazy to benchmark this myself but I'm also interested in the underlying reason why this may or may not impact my SELECTS.
Captain Crunch
ctpcr@hotmail.com
PS Win 2000 server, SQL Server 2000, 101 keyboard" |
|
|
|
|
|
Do smaller tables increase performance?