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.
A table in my database is expected to grow about 250,000 rows every year.
My fear is that it may slow down the client app, and probably pass the 30 sec runtime of MYSQL.
What should I do about this? Would MySQL be able to handle this, or I should go for a stronger ( IMO ) database like Microsoft SQL 2012?
250k rows is not huge. 10 million is still perfectly fine (40 years, I guess it won’t last that long), even half the time (20 years) would still be a long time for a software system.
If you create your queries properly, and set the right indexes, you should be fine. Always check with
EXPLAIN EXTENDEDif your indexes are properly used on a query.