Re: Tablespace size

On Feb 20, 5:44 am, "Neil Truby" <neil.tr...@ardenta.com> wrote: > And that, although it's fairly simple for an Informix God such as myself to > workaround, the same is not necessarily true of others;  that having to use > fragmentation not for its intended purpose but to get around an increasingly > wearisome product limitation is not consistent with the "Low Maintenance" > marketing message; and that it really needs to be addressed. > > So, Bollocks to you and your uninformed opinion!  (Which of course though I > fully respect as equally valid to mine). Neil, When you talk about a 'set it and forget it' database, how large are you really talking about? I mean lets take an example... a POS system sitting in a Wally*Mart. You only have so many SKU items. You have only so many transactions, which you can offload to corporate past 120 days if you like and then purge them from the system. (For RMAs you would want to track it in both the same store or either query the other store (peer to peer) or back to HQ.) So in the store, IDS works great because you're not really going to have to deal with a 16GB table space limit. While I chose a POS system, you can also choose an embedded application. Order entry for a mom & pop shop. Warehouse Distribution. Lots of applications don't even touch that limit. For those that do, we have guys like you and Art. ;-)