kramaswamy (2/2/2013)
IE, it wouldn't make sense to me to create one table called StoreTelephone, another table called StoreAddress, etc ...
Stores only ever have a single address and a single telephone number?
However, I'm working with a table right now which is approaching 30 columns - way more than I normally work with. All of these columns, though, are 1:1 relationships with the main identity. So to me, it wouldn't serve any benefit to branch some of these off into other tables.
If there's no benefit to moving some columns to another table, why are you considering moving them?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability