Yes, but I'm really lazy and changing one connect string is easier than going through
200,000 lines of code and changing table names. ;)
That's a good spin on it. Thanks.
--James
-----------------------
>From your message of Wed, 14 Mar 2001 14:09:30 -0600:
>Or, you could use one database, and lookup the clients table names, and
>use a merge table for reports.
>James Blackwell wrote:
>
> I have a similiar situation where I've got a huge database that maintains data for
>quite a few clients. Queries have gotten extremely sluggish.
>
> What I'm working on right now is to have a control database with a single table that
>contains a unique identifier for each client and a database name. When they log in
>it figures out the name of the database to use by looking in this table. Each
>instance of the program only accesses this one database (after finding it in the
>control) Since all of the programs that make up the suite call the same routine to
>establish a connection, it is a fairly painless update that I hope will provide
>substantial performance increases.
>
> The only drawback to this is if you need to run a lot of reports across clients. A
>few administrative reports wouldn't be so bad, but I wouldn't want to like construct
>a web page on the fly based on a query accessing 50 different data sources. Since
>this isn't the case here, it shouldn't be a problem.
>
> I'm by no means a guru, but this just seems like a logical way to handle the
>problem. If there is some major logic flaw here, please let me know now! ;)
>
> --James
> [EMAIL PROTECTED]
>
> -----------------------
>From your message of Wed, 14 Mar 2001 08:26:21 -0600:
>
>If all the data will be used by the same application then I would suggest
>that you stick with a single database.
>Cal
>http://www.calevans.com
>-----Original Message-----
>From: abdelhamid bettache [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 14, 2001 8:11 AM
>To: [EMAIL PROTECTED]
>Subject: use one database or many databases
>Hello,
> I have to design a huge database for all the universities , is it better
>to consider a database for each university or one for all universities ..
> If I consider one database so I'll have one table for all students wich
>contain about 300000 rows .
>thank you
>__________________________________________
>Get your free domain name and domain-based
>e-mail from Namezero.com
>New! Namezero Plus domains now available.
>Find out more at: http://www.namezero.com
>---------------------------------------------------------------------
>---------------------------------------------------------------------
>Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>To request this thread, e-mail <[EMAIL PROTECTED]>
>To unsubscribe, e-mail <[EMAIL PROTECTED]>
>Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
