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.
I would like some sugestion on how to design a table that gets like 10 to 50 million inserts a day and needs to respond quickly to selects… should i use indexes? or the overhead cost would be too great?
edit:Im not worried about the transaction volume… this is actually a assigment… and i need to figure out a design to a table that “must respond very well to selects not based on the primary key, knowing that this table will receive a enourmous amount of inserts day-in-day-out”
definitely. At least the primary key, foreign keys, and then whatever you need for reporting, just don’t overdo it. 10k-50k inserts a day is not a problem. If it was like, I don’t know, a million inserts then you could start thinking of having separate tables, data dictionaries and what not, but for your needs I wouldn’t worry.