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.
Are there any performance issues with having lots of empty tables in MySQL? My CMS system has loads of optional features, and the build script adds all the necessary tables to the database in case they’re needed in the future. Can anyone think of if and why this might be detrimental to performance? Disk space not really an issue…
I can’t think of any: In mySQL, a table consists of a number of files in the local file system.
Files laying dormant shouldn’t be a problem. (Well, except if you have thousands or tens of thousands of tables: That might cause trouble not so much for the database, but for the file system. But I doubt that is the case here.)