rjschappe wrote:

> I am starting to convert a MS SQL 7 database to FB 1.5 and I am
> wondering if I should continue to use an archive type of table
> (ArchOrderItem) or can I now roll these records back into my main
> OrderItem?
>
> The reason I originally removed these records from the main OrderItem
> table was to increase the speed of queries and reports.
>
> At the end of each month, any orders which were completly paid, were
> then moved over to the ArchOrderItem table.
>
> Now, all this was done waaaay back in MS SQL 6 and 6.5 when SQL
> server was slow and the hardware running it was slower... by moving
> these records out of the main OrderItem table, it made reporting much
> faster... but it makes reporting MUCH more complicated! I often have
> to run two sets of reports to include the paid orders and the non-
> paid orders - this is confusing to users too!
>
> I currently have just over 1 million rows on the ArchOrderItem table
> and usually add about 50,000 each month. Our new server hardware has
> lots of RAM (1 or 2 GIG) and a decent processer.
>
> Should I continue to archive my Orders and OrderItems or can I bring
> these back together???
>

That is so wierd, we do the same for a POS application, except that we
purge the temp sales tables (Order Records and Line Item Records) to the
"permananent" sales tables once a day. Our theory is the same as yours
about keeping queries quick because we used to use an Access DB then
moved to IB and finally, FB 1.5.

Please post your results as I am interested.


--

Warm Regards,

Lee