Database design question

#1

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch of
excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create 3
separate databases for each of these categories even though it is one
application. I have never seen this done before and am wondering if
there is a downside to doing this?

Thank you,
Joe

#2

Joseph Hesse:

Quote:

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch
of excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create
3 separate databases for each of these categories even though it is
one application.

Sounds like a great solution, Joe.
But....which problem does it solve?

#3

On 06/29/2011 12:37 PM, Erick T. Barkhuis wrote:

Quote:

Joseph Hesse:

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch
of excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create
3 separate databases for each of these categories even though it is
one application.

Sounds like a great solution, Joe.
But....which problem does it solve?

It is mainly for organizing the data. It also solves the problem of
backups. The only thing of importance is the real data tables. The
session information is temporal. The excel spreadsheets are used to
update the real data and then are no longer used.

#4

Joseph Hesse wrote:

Quote:

On 06/29/2011 12:37 PM, Erick T. Barkhuis wrote:
Joseph Hesse:

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch
of excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create
3 separate databases for each of these categories even though it is
one application.

Sounds like a great solution, Joe.
But....which problem does it solve?

It is mainly for organizing the data. It also solves the problem of
backups. The only thing of importance is the real data tables. The
session information is temporal. The excel spreadsheets are used to
update the real data and then are no longer used.

That's fair reasoning. But... are the volumes of data in the session and
temp tables particularly large? Also, presumably, after the excel data is
uploaded and processed, you could drop the rows so that backup size will be
trivial...

Also, backing up all tables at least ensures you do have a schema backup at
all times. It would be easy to make schema changes to the session tables (et
al) and forget to take a dump.

Cheers,
Tim

--
Tim Watts

#5

Joseph Hesse wrote:

Quote:

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch of
excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create 3
separate databases for each of these categories even though it is one
application. I have never seen this done before and am wondering if
there is a downside to doing this?

Thank you,
Joe
yes. Why separate data that belongs to one and only one app.

#6

Joseph Hesse wrote:

Quote:

The tables in my DB, from a design point of view, fall into 3
categories. They are the real data, session information and a bunch of
excel spreadsheets converted to MySQL tables.

Currently everything is in one MySQL DB. It occurred to me to create 3
separate databases for each of these categories even though it is one
application. I have never seen this done before and am wondering if
there is a downside to doing this?

Yes.

<http://www.catb.org/~esr/faqs/smart-questions.html>

--
PointedEars

Bitte keine Kopien per E-Mail. / Please do not Cc: me.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Database design question

comp.databases.mysql comp.databases.mysql

Database design question - 06-29-2011 , 11:42 AM

Re: Database design question - 06-29-2011 , 12:37 PM

Re: Database design question - 06-29-2011 , 01:10 PM

Re: Database design question - 06-29-2011 , 01:25 PM

Re: Database design question - 06-29-2011 , 07:32 PM

Re: Database design question - 06-29-2011 , 07:45 PM