Preface
To export a production or productions components for deployment using Interoperability > Manage > Deploy Changes > Deploy, the export of persistent classes that are part of a deployment (typically message classes, but there can be others) include table statistics and, at the moment, there is no option to disable exporting statistics (i.e. use /exportselectivity=0 qualifier).
Description of the idea
The idea is to exclude table statistics in the Production export or at least have the option of disable it during export.
Who is the target audience?
Anyone using Production Export
What problem does it solve?
Exporting table statistics along with persistent class code/definition has many disadvantages, for example the statistics of a development environment usually are not suitable for a real production environment.
Another example is that Statistics may contains actual data (i.e. outlier values) that, in some case, can be confidential data and you don't want to include confidential data in the export.
Note that it might be possible (using an undocumented hidden feature) not to IMPORT statistics during deployment, but this is less optimal/convenient because it does not address the distribution of confidential data (outliers) and rely on the final deployment stage for not messing up table statistics. Ideally you want to avoid it from the beginning during export.
How does this impact the efficiency, stability, reliability, etc, of the product?
If statistics are removed from persistent classes export then you don't mess the environment where you deploy.
Provide a specific use case or scenario that illustrates how this idea could be used in practice.
We had issued o performance AND (potentially) confidential information (outlier values).
Please consider this idea for the current ongoing contest.
Thank you for submitting the idea. The status has been changed to "Future consideration".
Stay tuned!
