Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
these tables will be constantly inserted new rows or updating.
i have a big table containing, video url, title, description, tags, views, rating, comments
should i divide this to 2 smaller tables
id video url, title, description
and link this to above.
id video_id, tags, views, rating, comments
It doesn’t sound like your tables are very normalized. You want to avoid storing duplicate data, unless it has some performance benefit. Duplicating information will lead to larger record and index sizes, which can increase disk seek time.
If the columns you listed are as self-explanatory as they sound, then I would break it into three tables:
videoId,url,title,description,rating,viewsvideoId,tagvideoId,commentThis will allow you to have a single entry for each video, storing the primary information just once. You can then relate a video to multiple tags and multiple comments.