| Subject | RE: [firebird-support] Re: Desgin question - Mutiple years of data, single database or many? |
|---|---|
| Author | Rick Debay |
| Post date | 2009-08-19T15:34:53Z |
We keep everything, and make sure to have appropriate indexes on date
fields. The only problem we ever have is when we fail to include a
constrain the date range on large calculations.
We archive data only when it is older than various data retention
mandates, usually five or seven years. Then it rots on a tape in a
safety deposit box.
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Bhavbhuti
Nathwani
Sent: Monday, August 17, 2009 1:59 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: Desgin question - Mutiple years of data,
single database or many?
Thanks a lot Geoff you have explained everything I have faced in a very
details manner. First of all it was a relief to know that what I was
doing was not out of the world. As per your suggestion I am fine with
summarizing the previous years data that is needed in the current years
database reporting.
Now that you have been through this and have managed it, I would like to
ask you about outstanding receivables. I have currently kept a flag
field in the invoices tables which is set to true if an invoice belongs
to the previous (or still older) year so that it will remain readonly
and will not have any relevance in accounting except for bill-to-bill
adjustments for debtors list and o/s letter purposes. These such o/s
invoices are not removed in the end-of-year processing until they are
either written-off or adjusted completely in the current year. Is this
way of mine good in your views? Do you have any suggestions for this.
Thanks and regards.
Bhavbhuti
Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.
fields. The only problem we ever have is when we fail to include a
constrain the date range on large calculations.
We archive data only when it is older than various data retention
mandates, usually five or seven years. Then it rots on a tape in a
safety deposit box.
-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Bhavbhuti
Nathwani
Sent: Monday, August 17, 2009 1:59 PM
To: firebird-support@yahoogroups.com
Subject: [firebird-support] Re: Desgin question - Mutiple years of data,
single database or many?
Thanks a lot Geoff you have explained everything I have faced in a very
details manner. First of all it was a relief to know that what I was
doing was not out of the world. As per your suggestion I am fine with
summarizing the previous years data that is needed in the current years
database reporting.
Now that you have been through this and have managed it, I would like to
ask you about outstanding receivables. I have currently kept a flag
field in the invoices tables which is set to true if an invoice belongs
to the previous (or still older) year so that it will remain readonly
and will not have any relevance in accounting except for bill-to-bill
adjustments for debtors list and o/s letter purposes. These such o/s
invoices are not removed in the end-of-year processing until they are
either written-off or adjusted completely in the current year. Is this
way of mine good in your views? Do you have any suggestions for this.
Thanks and regards.
Bhavbhuti
Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.