elmas156 Posted August 20, 2008 Share Posted August 20, 2008 This one seems pretty basic but I haven't been able to find the answer yet... How many tables can I create in one database? Just curious. Thanks. Quote Link to comment Share on other sites More sharing options...
revraz Posted August 20, 2008 Share Posted August 20, 2008 Not really sure, but I don't see why there would be a limit. Quote Link to comment Share on other sites More sharing options...
cooldude832 Posted August 20, 2008 Share Posted August 20, 2008 I don't think there is a limit but why would u need so many tables? Quote Link to comment Share on other sites More sharing options...
Mchl Posted August 20, 2008 Share Posted August 20, 2008 It depends on the database brand. For mySQL there's no limit Quote Link to comment Share on other sites More sharing options...
fenway Posted August 21, 2008 Share Posted August 21, 2008 It depends on the database brand. For mySQL there's no limit At some point you'll hit the FS limit on files.... but you'll hit other practical limits way before them. Quote Link to comment Share on other sites More sharing options...
AjBaz100 Posted August 22, 2008 Share Posted August 22, 2008 Yes there is a limit, but it depends on the OS running the database and the table types. If you create InnoDB you can usually create many more tables than say MyISAM. MySQL will keep creating tables in either case, but you will soon run into trouble from the OS and the amount of file handles, which does have a finite limit. Quote Link to comment Share on other sites More sharing options...
bluejay002 Posted August 22, 2008 Share Posted August 22, 2008 On the contrary, InnoDB is more or less 3x larger than MyISAM. Use InnoDB whenever you have lots of writes and transactional operations. Also, MyISAM runs faster for read compared to InnoDB. Going back to your question, I don't think it is something you should worry about. Most of the case, you will create different databases for different purposes and just cross-reference with it whenever necessary. Quote Link to comment Share on other sites More sharing options...
Mchl Posted August 22, 2008 Share Posted August 22, 2008 On the contrary, InnoDB is more or less 3x larger than MyISAM. Thing is, MyIsam stores each table in separatae file, which may be a problem with some filesystems. On the other hand, it's easy with MyISAM to spread tables over several folders/partitions. Also, MyISAM runs faster for read compared to InnoDB. A post I've read recently on MySQL Perofrmance Blog shows something different. Although I agree that syntetic benchmark like the one used doesn't catch all nuisances of real production environment. Nevertheless I recommend reading it. Quote Link to comment Share on other sites More sharing options...
bluejay002 Posted August 22, 2008 Share Posted August 22, 2008 A post I've read recently on MySQL Perofrmance Blog shows something different. Yeah... I have read it before. I don't think it's always true. We have tried changing some tables to InnoDB and realyl became slower with its size to have grown dramatically, of course we are aware that might happen but it is something necessary because of transactional operations. Anyway, I do not know if they converted it back after their checks (am only in the background). It may different to anyone though, so you try and apply which ever applies best for you. Quote Link to comment Share on other sites More sharing options...
Mchl Posted August 22, 2008 Share Posted August 22, 2008 I need transaction support. Period. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.