November 16, 2006 at 5:39 am
Introduction
I am designing a database for an application, which will have
1. At least 100 tables, which qualifies for all the rules for normalization.
2. Five major processes doing intensive mathematical calculations. These processes will then dump the processed data into separate tables. These tables will be queried throughout the other processes and will have an addition of 50000+ records each month.
And we need to keep 24 months of data at any time for reporting which means each of the tables
will have at least 1.2m rows at any given time. Each table will have a year & a month field to distinguish the data.
Questions
1. What type of architecture/design/technique should I use to obtain maximum performance & better maintainance?
2. Any idea about design practices and patterns one should follow for designing a new database for large online applications.
3. Any good resource on Internet and books regarding the problem.
--Ramesh
November 16, 2006 at 9:13 am
Based on my experience, you may consider the business intelligence (BI) design. However, based on your description, your database is not huge at all. I believe a regular design should be okay.
November 17, 2006 at 1:04 pm
One additional thought is to partition the tables based on the month. This will allow you quick and easy maintenance when archiving and purging data. The additional benefit is that it wikll helop wou in certain daily maintenance tasks as well.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply