Log table change dbspace
Sergio Peres wanted to move a fast-growing log table with many indexes and relations to another dbspace. Alexandre Marini suggested creating a new table and loading it (external tables are fastest), loopback ER replication, or rolling-window partitioning (Enterprise only), and questioned keeping logs in a relational table. Sergio said he would test the advice.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi, I have one table for log that grow a lot, I would like to move it to another dbspace. But that table have several indexes and relations to another tables. How can i do it? Thanks for any help, SP sergio.peres@airc.pt
Hi, Sergio. Since you did not mention your engine version and edition, I don't know if you can have so many options. But Informix in all editions, offers some ways to achieve that: 1) create an empty table, optimized as you wish, and export/import the data using unload/load, select/into, or even external tables (faster way). 2) you can use loopback ER replication for that new table, and then replace it easily online 3) logs generally can have small amount of retention, so I would think about partitioning with rolling window features (but this is an enterprise feature edition only) My real question would be "why do I store application logs into relational table? I can now use NoSQL, or even an external table...". Of course that will depend on how much do you use it for reports, since you told you have several indexes and referential integrity, right? Hope that gave you some nice ideas for improvements. Best regards Alexandre Marini
Hi Alexandre, Thanks for your reply, I will take a look to your advices. We are doing some tests as we are facing some problems over some customers that have the highest level log selected. SP
Hi Alexandre, Thanks for your reply, I will take a look to your advices. We are doing some tests as we are facing some problems over some customers that have the highest level log selected. SP