[Perfparse-users] Help Needed

[Ben C. <Be...@cl...>]

Dear Users,

When the current versions are stable, we will be looking to convert the 
binary table in the PP database.  This will probably take our product up 
to version 1.0.  I need some advise from users about the best method.

The advantages of the change are:
- A range for the Warn and Crit values, rather than just a single value.
- Smaller storage space needed for same data.
- Faster access to data, bigger graphs possible.
- A scalable solution where new information can be added easily.

In order to complete this conversion, the main table 
'perfdata_service_bin' will be copied to two new tables, and then 
dropped.  But this causes problems.  In order to complete this 
conversion there are three methods.  I would like you to suggest which 
one you consider the best.  Then we will program and use the method you 
choose.   Please let us know.

Option 1.
---------

Copy the old table to new tables and delete old table.

Pro:
   Fast.
   Easy to program & test => low in bugs.
Con:
   Will double size of MySQL database during conversion.
     This space is very hard to recover.


Option 2.
---------

Copy all data to an external text files.  Delete old table.  Copy back 
to new tables.  Delete text files.

Pro:
   Fast.
   No increase in MySQL table space.
Con:
   Harder to program & test => bugs possible.
   Text file size is far larger than table, which is binary.
   Need database size again in temporary storage for text dump of table.


Option 3.
---------

Copy over a line at a time and delete line from old table.

Pro:
   No extra space needed.  No increase in MySQL table space.
   Easy to program & test => low in bugs.
Con:
   Deleting line by line is slow.  Conversion may take several weeks.


Finally, a plee to anybody who knows some MySQL and a little 'c'.  Can 
you spare some time to help develop and/or test a conversion program. 
You time will be welcome, and you will be credited as a developer.

Kind regards,

Ben Clewett.