Which is better. To rather have many tables or have everything squeezed in a few tables? I'm talking about hundreds of tables... IMO it would be more professional to have separate tables, just worried about the performance.
Wrong forum, but we need more information on what you're trying to accomplish before giving you any advice.
I'm coding a rpg game and I want to log everything, I just don't know if I should create a separate table for each page... Having more tables might utilize more server memory?
It depends on how much data you have and how it will be accessed. I had one 7 gig table that was very slow but any given query only wanted a small section of it. Breaking it into 68 tables made each of those queries MUCH faster. I have over 200 tables in all. If each of your pages only needs access to a small amount of the table, and it's always the same section, then breaking them into smaller tables will usually be faster. For example, if page1.php only ever accesses Big-Table where Column1 = 'page1' then making a page1 table makes sense. It keeps the server from having to look at thousands of 'page2' entries to find 'page1.' However, if page1.php sometimes checks where Column1='page2' then you should keep it together; joins are slow. Make sense?
This is a very debatable topic and I don't think there is a correct answer. Take a project like wordpress. They stuff data into tables in ways that would not be considered a good practice. But, it's a simple schema, and it works. As far as most best practices are concerned, table numbers shouldn't be a concern, provided that they are created in a logical and relational manner. Don't store data in non relational formats (ex: deliminated data in a field) which is something that wordpress does. If you're worried about performance, then I would actually lean towards more tables. Selecting from massive tables with many rows can destroy the usability of an app. What Goramba is describing is basically partitioning where you break a large data set into smaller ones to increase the database's speed, which can be a major concern for large tables and limited resources.