To be honest not sure if this is required or not, but I will often after a manual DMT of a file run it through a “save as compacted copy” to save some space, and this does seem to reduce the file size a little from it’s post-DMT size.
Keen to know whether this is really necessary and if so would it be useful to add an option post deployment to compact the newly migrated file to conserve space ?
This might be useful also when installing/replacing a file as opposed to migrating also. I believe this is something the command line developer tool can do.
I think there is case to make it easier for to do this regardless of migration or deployments. It would just be a useful thing to be able to do. File’s build up extra space under normal daily operations. What if you could schedule a compact? Have it run once a week.
We could just add it to the UI in OttoFMS so you could run it on demand too.
If you did that you probably wouldn’t need to do it as part of a deployment.
+1 for this feature. It just came up at Codence’s Nerd Out chat, too – a colleague mentioned that he’s got a client where he would want to always run the compaction after the migration ran (in the latest instance, it went from 24GB to 16GB when compacted immediately after DMT merge).
Compaction can definitely be done via the developer tool CLI. Would be great to have it as a checkbox option for a post-migration action.
This would be super helpful. Files regularly end up with extra space in them after running the DMT. As Cristos mentioned, I used Otto last week to roll data from an 18 GB file into a clone and the resulting file was 24 GB. I compacted it using the FMDeveloperTool which brought it down to 16 GB. It would be great to have that as an automatic option in Otto.
@toddgeist I agree that it would be nice to have it as part of the OttoFMS tools. But I don’t think that necessarily negates the want to have it as an option at the end of an Otto deploy.
Either option is fine, though I usually tend to do it post deployment but that’s just because it’s a convenient time to do it while the file is offline.
I do have some solutions that run 24/7 so taking it offline to compact is not an option, hence during a deployment window is best.
I just came across a use case for scheduling a “file-cleanup-in-place” today.
I’m not sure how much of a difference between using DMT and a compacted copy, but I’ve heard that it is better to do a migration rather than a compacting. Either way, it would be a nice use of Otto to run a weekly cleanup
