I've noticed that it seems like these autoinstallers want to install each script with its own database. At that rate, it's no wonder some hosting plans allow lots of databases, but what about those who don't? If, say a plan allows 2 databases, but they want to install 3 things from the autoinstall options means they'd have to install 1 by manually adding the tables to another database that was created from another autoinstall script? I thought mySQL could support multiple connections and tons of tables. Why do these installers want a seperate database for each install instead of just adding tables to a current database?

Generally each peice of software requires 1 database to itself, autoinstaller or not. It gets VERY messy when you have more than one peice of software in a single database.

Ofcource it is possible, but not wise.

Organizationally speaking it's just neater. You don't really have to provided you start each table with a program ID. For instance In one DB I run PHP-Nuke and CyDock, all nuke tables start with nuke_ and all CyDock tables start with cydock_.

aNc

you can use 1 db for all, but most hots will give you 2-3-4 DB`s for free or small setup fee.

With a Windows host and MS Access, you're basically allowed unlimited databases automatically. But then again, MS Access has a fairly low concurrent connection limit per database, so you basically need everything on seperate databases. But if these tables were in something else, it seems like they could be combined. I was just wondering what the idea was behind this whole concept. Maybe to bring in additional revenue for more databases?