Hosting MySQL databases?

While sitting in a puddle William Tasso scribbled in the mud:

 > Duende wrote:
  >> To a host, what is the difference between a customer having 10
  >> databases with each having 1 mb of stuff in it or 1 database with 10
  >> mb of stuff in it also assuming an equal number of tables.
 >
 > Resources. A small db uses less RAM, however each db has its own
 > overhead.
 >
 > Usual advice is to have one db containing all your data and that works
 > well in most circumstances. It may be sensible to place rarely used
 > data in another db.
 >
 > Why?
 >

Just seems more neat & tidy to have all tables pertaining to each thingy in
their own database. Maybe I need just one big thingy instead if many snall
thingys.

--
Duende<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

Duende wrote:
 > While sitting in a puddle William Tasso scribbled in the mud:
 >
  >> Duende wrote:
   >>> To a host, what is the difference between a customer having 10
   >>> databases with each having 1 mb of stuff in it or 1 database with 10
   >>> mb of stuff in it also assuming an equal number of tables.
  >>
  >> Resources. A small db uses less RAM, however each db has its own
  >> overhead.
  >>
  >> Usual advice is to have one db containing all your data and that
  >> works well in most circumstances. It may be sensible to place
  >> rarely used data in another db.
  >>
  >> Why?
  >>
 >
 > Just seems more neat & tidy to have all tables pertaining to each
 > thingy in their own database. Maybe I need just one big thingy
 > instead if many snall thingys.

There is economy of scale to factor in. For example if you have a db that
contains your site navigation/site map then it could make sense to have just
one set of routines that delivers to several sites based on a parameterised
query: what site is calling?, what page is calling?

Then you only have your logic and data in one place - easy to manage change.

Same can apply to many apps, guestbook, forums, online polls etc....

--
William Tasso<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

"William Tasso" <SpamBlocked DeleteThis @tbdata.com> wrote
 > Usual advice is to have one db containing all your data and that works
well
 > in most circumstances. It may be sensible to place rarely used data in
 > another db.
 >
 > Why?


Some web-based programs such as guestbooks, bulletin boards, etc, like to
use their own database...or two. Drives me nuts <!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

"Duende" <xxxspam.DeleteThis@wipkip.biz> wrote in message
news:Xns949DD58CE79A9xxxspamwipkipbiz@130.133.1.4...
 > To a host, what is the difference between a customer having 10 databases
 > with each having 1 mb of stuff in it or 1 database with 10 mb of stuff in
 > it also assuming an equal number of tables.
 >
For us - it is 10 mb - thats all she wrote.

By the way mr D. do you ever sleep?<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

While sitting in a puddle Bill Logan scribbled in the mud:

 > By the way mr D. do you ever sleep?

Gave that up years ago. Just a waste of time.

--
Duende<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

"Duende" <xxxspam.DeleteThis@wipkip.biz> wrote in message
news:Xns949DD58CE79A9xxxspamwipkipbiz@130.133.1.4...
 > To a host, what is the difference between a customer having 10 databases
 > with each having 1 mb of stuff in it or 1 database with 10 mb of stuff in
 > it also assuming an equal number of tables.

In most cases it would be a waste of resources

Having multiple databases is necessary in some cases... but for the most
part if you just want to keep it "neat and tidy" and have a database for
your products, a database for your guestbook, a database for your sitemap, a
database for wholesale products, a database for people signed up for your
newsletter... etc... etc...

It just ends up being a waste of system resources (RAM, cache, CPU, etc) if
you are opening a database connection, reading a table, closing database
connection, opening new connection, reading a table, closing connection,
opening a third connection, etc, etc, etc<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

"Duende" <xxxspam.DeleteThis@wipkip.biz> wrote in message
news:Xns949E10B7DF680xxxspamwipkipbiz@130.133.1.4...
 > While sitting in a puddle William Tasso scribbled in the mud:
 >
  > > Duende wrote:
   > >> To a host, what is the difference between a customer having 10
   > >> databases with each having 1 mb of stuff in it or 1 database with 10
   > >> mb of stuff in it also assuming an equal number of tables.
  > >
  > > Resources. A small db uses less RAM, however each db has its own
  > > overhead.
  > >
  > > Usual advice is to have one db containing all your data and that works
  > > well in most circumstances. It may be sensible to place rarely used
  > > data in another db.
  > >
  > > Why?
  > >
 >
 > Just seems more neat & tidy to have all tables pertaining to each thingy
in
 > their own database. Maybe I need just one big thingy instead if many snall
 > thingys.
 >
In MySql you would manage that in one db by giving rhe tables for each
thingy a group prefix - as in big_thingy for all tables for big thingys and
small_thingy for all tables for small thingys.

Then it is simple when you need to identify one group of thingys from
others.

--
bildanet
MyLot.net - the home of the $10 reseller programme<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

While sitting in a puddle Bill Logan scribbled in the mud:

 > In MySql you would manage that in one db by giving rhe tables for each
 > thingy a group prefix - as in big_thingy for all tables for big
 > thingys and small_thingy for all tables for small thingys.
 >
 > Then it is simple when you need to identify one group of thingys from
 > others.

That's what I have to do on some sites.

Mostly it was something I was just wondering about.

I have 4 hosts that use cPanel and only one of them sets a limit. As it's
one of the best I thought they must have a good reason whereas the other
best one doesn't set a limit.

--
Duende<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases? 

While sitting in a puddle Augustus scribbled in the mud:

 > Duende" <xxxspam RemoveThis @wipkip.biz> wrote in message
 > news:Xns949DD58CE79A9xxxspamwipkipbiz@130.133.1.4...
  >> To a host, what is the difference between a customer having 10
  >> databases with each having 1 mb of stuff in it or 1 database with 10
  >> mb of stuff in it also assuming an equal number of tables.
 >
 > In most cases it would be a waste of resources
 >
 > Having multiple databases is necessary in some cases... but for the
 > most part if you just want to keep it "neat and tidy" and have a
 > database for your products, a database for your guestbook, a database
 > for your sitemap, a database for wholesale products, a database for
 > people signed up for your newsletter... etc... etc...

Thanks fo everybodys input to my question. I think I might have learned
something.

--
Duende<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Hosting MySQL databases?