Re: Handling of Year wise data in Database Design

[Peter Brawley]

>Is it possible for u to send the table structure for Accounts.

That would require a full use case analysis. Beyond the scope of a forum.

>If there is any MySQL feature which segment a set of transactions
>say transactions for a particular year in the table except the
>filtering option which will restrict the performance when the
>table get multiple years of data?

There are several ways to approach that. One is via partitioning, which you should read abpout in the 5.1 manual. A second is to create an OLTP database to run the current year or two, an OLAP cube to analyse history, and a module that moves data from former to latter as desired. A third way, less ambitious, is to maintain past years in an archiving readonly system which has the same structure as the active system, moving data to the archive as desired.

PB