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 |
|
Blastrix
Posting Yak Master
208 Posts |
 Posted - 2001-05-11 : 11:50:42
|
| When should you index a column? When shouldn't you? Even in the name of normalization, how much is too much, or rather how many tables is too many tables? Say I have the following table:users---------userIdusernamepasswordemailfirstRegisteredlastVisitbannedAll of those fields will have a value so there will be no nulls there. That doesn't seem hard, the next table is kind of tricky, it contains all the personal information about people if they choose to enter it.userDetails-------------userIdrealNameicqcitystatecountrybiobikeTypebikeModsAny or all of the above fields may be filled in by the user. But at the same time, they could just enter their name, and all the other fields would be nulls or 0. Is that good design or should I break it down more? |
|
|
|
|
|
To index or not to index and other stuff