Hi All.

I'm working on quite big database. It consists of about 200 tables.
Additionaly about 50 tables are per year (because of annual data). It
means every year new 50 tables will have to appear in application. And
now I have a question. Should I use separate databases for "annual"
data (i.e. db2006, db2007, etc...) (i don't need constraints on that
(annual) tables) or put all the tables in one database? Is there any
way to 'catalogue'/organize tables within one database (namespace/
schema)?

Any thoughts?
Thanks in advance...

EMAIL REMOVED wrote:
> Hi All.
>
> I'm working on quite big database. It consists of about 200 tables.
> Additionaly about 50 tables are per year (because of annual data). It
> means every year new 50 tables will have to appear in application. And
> now I have a question. Should I use separate databases for "annual"
> data (i.e. db2006, db2007, etc...) (i don't need constraints on that
> (annual) tables) or put all the tables in one database? Is there any
> way to 'catalogue'/organize tables within one database (namespace/
> schema)?
>
> Any thoughts?
> Thanks in advance...
>

one way of doing this is to separate your archived (annual) data from
the operational data you have. migrate the archived data to a separate
database, use archive engine for engine type to save data by compressing
the data if there are no changes to the data. there is no need to
separate the years in my opinion; however, try adding some sort of a
column in your tables to distinguish between different years (maybe a
dbyear column).

hope this helps.

--
lark -- EMAIL REMOVED
To reply to me directly, delete "despam".