List:General Discussion« Previous MessageNext Message »
From:Przemysław Klein Date:May 22 2007 7:57am
Subject:design choice - quite many tables
View as plain text  
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...

-- 
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
Przemek Klein (p.klein@stripped)

Thread
design choice - quite many tablesPrzemysław Klein22 May
  • Re: design choice - quite many tablesBrent Baisley22 May
  • Re: design choice - quite many tablesMartijn Tonies22 May
    • Re: design choice - quite many tablesPrzemysław Klein23 May
      • Re: design choice - quite many tablesWm Mussatto23 May
        • Re: design choice - quite many tablesPrzemys?aw Klein24 May
          • Re: design choice - quite many tablesWm Mussatto24 May