Database design issue: Split tables or not?

[envida]

I have problem deciding if I should split up some tables or not.
I have linked a picture so you can better understand what I mean.

http://forums.databasejournal.com/clear.gif

As you can see in the image I have categoryID as foreign key in tblBlog and blogID as foreign key in tblComment , but I was thinking that maybe I should rather but blogID and categoryID in new table and related them there. The same with blogID and categoryID.
The picture shows both implementations.
Anyone have a recommendation for this? I'm guessing that if the database have a large amount of data it would be best to have new table. But in this case a maximum would maybe a couple of thousand at most...
Also the queries would be less work if I have fewer tables.

Any help is welcome and appreciated.

Cheers

[MAK]

if you are not going to search on the table (like fulltext) then split the table or else keeping it in the same table is better.

It is not always golden thumb rule to normalize data.

We trade normalization for performance in many occasions.