We have clients that want data over years; we distill that into weighted average data. In some cases we turn minute or 90 second timestamped data into 10 or 15 minute weighted average data and save that instead of the actual data for a year.

The weighted average data takes about 1G, where the current year takes 6-10G. So, we keep 1 year of actual timestamped data and 1 year of weighted average.


If it is inventory or sales, you can keep an aggregate of sales over a week, month. or quarter for everything over one year. For timestamped data, this is much easier, but your inventory should be manageable this way.

Kurt.
----------------------------------------
Never underestimate the Power of Denial.

>
>From: Bhavbhuti Nathwani <venussoftop@...>
>To: firebird-support@yahoogroups.com
>Sent: Monday, August 17, 2009 10:32:08 AM
>Subject: [firebird-support] Re: Desgin question - Mutiple years of data, single database or many?
>
>
>Hi Anderson
>
>>Thanks for your reply. What I have missed to mention is that I had an Accounting and Inventory system in mind when I wrote this question. If I may ask, is your application similar? How big is the database? How many years do you currently have in it?
>
>>Thanks for the suggestion that I continue my system and do something to maintain the summary data required. One typical problem that I have faced and will face is for eg. receivables outstanding. Wherein invoice data of the previous year needs to be maintained long after end-of-year processing has been run for bill-to-bill adjustments. What I had done was to have a logical field which would be tripped to be true if data is carried over from last year so it would not have any relevance in the reporting for the current year. In this regards if you have any further suggestion please let me know.
>
>>Kind regards.
>>Bhavbhuti
>
>>--- In firebird-support@ yahoogroups. com, "Anderson Farias" <peixedragao@ ...> wrote:
>>>
>>> Hi,
>>>
>>> > I am sure people here have had to report data from multiple years as well
>>> > as reports like Stock Ledger which
>>> > mostly requires the current set but starts with summarized data for
>>> > Opening Stock. What have they done?
>>>
>>> Hi, my experience is having all years on same database, but I'm don't have
>>> idea if you should change the way you do it as it have beem working good for
>>> you.
>>>
>>> As I understand all you need is summary data from previus years, than, my
>>> sugestion would be to create those "sumary data" tables you need on your
>>> current (year) database and use something as and ETL tool to
>>> extract/transform data from previus database (years) to the current one.
>>>
>>> That way you don't change anything and have the data you need for this
>>> specific report.
>>>
>>>
>>> Regards,
>>> Anderson
>>>
>
>
> > >

[Non-text portions of this message have been removed]