|
-
Jul 8th, 1999, 12:15 AM
#3
Thread Starter
New Member
I am by no means a database design guru, the table contains info about clients, each row is a different client, each column a unique attribute of the client. I obviously could break the table into many tables, but then I woud have 1 to 1 relationships abounding, and lots of JOINS in my SQL.
I sort of assumed that KISS was wise, and large and simple was better than small and complex. But I don't really know which is better.
Are there any rules-of-thumb for how many columns tables should have?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|