I discovered by accident that I can link any website
on my reseller account to one database. That would be
far more convenient than working with six separate
databases, and it would also cut down on file size
overall, since there are certain tables that I share
between websites.
But my host
David Blomstrom said:
I discovered by accident that I can link any website
on my reseller account to one database. That would be
far more convenient than working with six separate
databases, and it would also cut down on file size
overall, since there are certain tables that I share
between
Your theory that more tables won't slow down a client if it doesn't
access them is correct, it won't slow the client down. But it's slowing
down the server that you should be worried about, not the client. The
more tables you have, the more file handles MySQL has to have open
along with
--- Brent Baisley [EMAIL PROTECTED] wrote:
There are advantages to one large
table over many
smaller tables. A large table will take advantage of
query caching
better (if you have query cache enabled). Lots of
smaller table would
probably cause the query cache to get flushed more
often.
show variables like 'query%';
That will show you the setting for mainly your query cache. The
query_cache_type will tell you if it's on or not.
On Mar 23, 2005, at 3:08 PM, David Blomstrom wrote:
--- Brent Baisley [EMAIL PROTECTED] wrote:
There are advantages to one large
table over many
smaller
