huge "xml storage" table

[MrSarna]

Hi everybody,

I have OTRS 3.1.5 installed on a Debian Squeeze server working with PostgreSQL 8.4 on Debian Squeeze. I was shocked when see that one of the tables (xml_storage) weighed 28 Gigabytes. It seems to me, that the database grow has something to do with the daily updates I make with the data from OCS Inventory.

So, my question is: Does the table xml_storage save some kind of historical data I can get rid of? Why is it so big?

I have 1890 items on the CMDB.

Thanks in advance,

Alfredo

[jojo]

yes, it safes historical data. You seem to update your inventory even if not neccessary. So you should check which values are changing on your CIs

[MrSarna]

Thanks for your help. I knew it had something to do historical data, but how do I know which information can be deleted? Are the scripts for deleting such information?

Alfredo

[jojo]

you can only delete the CIs, but not part of it

[MrSarna]

I found a a forum post related to the subject viewtopic.php?t=17326&p=67750. The person suggest to delete all the table rows where xml_type == "ITSM::ConfigItem::Archiv".

I'm not sure if this is a proven method but it seems to make a lot of sense to me. I'm going to try it on a testing environment and let you know the outcome.

If anybody has an idea to solve this situation, please let me know.


Alfredo

[MrSarna]

I tested the solution on my production environment and its working fine. There doesn't seem to be any problem. Indeed the application its running way faster than before, specially the searches on the CMDB interface.

Greetings,