>Hi,
> I am developing Retails POS system. Therefore, the number records of sales, sales item, and other such as log/transaction will grow and grow. For improvement of performance and also table capacity limitation, I would like to have PURGE function for my client.
> I have a question here, the transaction/log records may be used for certain module for calculation, validation and etc. THerefore, once the records being purged, the particular module may not able to return correct result to user. What should I do, in order to solve these problems?
>
>Thank you
Well, the easiest solution would be NOT to use a transaction/log file, and keep everything in the main table. Do you really think you will surpass 2e9 bytes for any single table in the foreseeable future?
As to speed, this can usually be solved with Partial Rushmore Optimization for tables and views, and using views for child tables.
HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
