Does it matter if you have one DB (but multiple tables) for the whole web site? In my case, it's 3000 HTML pages going into 1 DB, but into perhaps 30-40 tables. I thought I would have one DB with all the lookup tables and tables that several other tables will link to, and one DB with all the data tables. I thought this would keep things neater. Are there good reasons to break a DB into 2 or more? What are those reasons?
SQL CREATE DATABASE database_name CREATE TABLE table_name ( column_name1 data_type, column_name2 data_type, column_name3 data_type, )
Generally each application has single database.. having 30..40 tables is not big. some people keeps one more database for reporting or analytics its all depends on your requirement.
I am maintaininga a project where the DB has more than 300Tables. I have no problem in maintaining it!! Dont beleive? check the screen shot
One per application is plenty. Unless you have separate sites linking to each other using integrations etc. Databases are scalable, 30-40 tables is very little