i'm coding a forum (just for fun learning sql) and i have a question about tables.
I have a table called groups and the table contains two fields groupKey (pkey), and title.
In the title field i have: Java, Vb, Vb.NET, and C#
Then in another table called Topic_headings I will store all the header information for each posting (the title of the post). ex java help, vb help.. etc.
now my question: would it be better if i create multi tables for each group as Topic_headings. such as vb_Heading, C#_Heading, java_Heading, etc. instead of just having one group called Topic_headings.
The reason why i ask. wouldn't it be faster/better on the server if all the data was stored in more of a uniform, than having the sql eng search through all the headings just for say all java headings? or is this bad pratice?
If this post is making you scratch your head please please tell me.. i will think of another way to post my question. I would really like to know the answer.
cheers.
--------------
I have a table called groups and the table contains two fields groupKey (pkey), and title.
In the title field i have: Java, Vb, Vb.NET, and C#
Then in another table called Topic_headings I will store all the header information for each posting (the title of the post). ex java help, vb help.. etc.
now my question: would it be better if i create multi tables for each group as Topic_headings. such as vb_Heading, C#_Heading, java_Heading, etc. instead of just having one group called Topic_headings.
The reason why i ask. wouldn't it be faster/better on the server if all the data was stored in more of a uniform, than having the sql eng search through all the headings just for say all java headings? or is this bad pratice?
If this post is making you scratch your head please please tell me.. i will think of another way to post my question. I would really like to know the answer.
cheers.
--------------