Re: Tables vs. databases

On Fri, June 9, 2006 12:10 pm, Antonio Bassinger wrote: > > I've a HTTP server. I intend to run a file upload service. There could > be up > to 10000 subscribers. Each saving files up to 10 MB. > > I made a proof-of-concept service using PHP & MySQL, where there is a > single > database, but many tables - a unique table for each subscriber. But I > realize that I may land in trouble with such a huge database. Would it > be > better to have a separate database for each subscriber? > > Which approach is better, many tables in 1 database, or many databases > with > 1 or max 2 tables? > > Kindly suggest with pros and cons of each. The one-database-for all method increases risk that an SQL error will "leak" information from one client to another. The overhead for multiple databases is tiny, except maybe in god-like "admin" pages that would access 2 databases at once. You do have to be methodical about db changes and applying them to ALL the dbs at once, or you'll have a version-control nightmare quickly... -- Like Music? http://l-i-e.com/artists.htm