KB485192: How to retain Enterprise Manager staging statistics table data in MicroStrategy 2020 and above?

QUESTION:

How to retain Enterprise Manager staging statistics in Strategy 2020 and above?
In the scenario of troubleshooting relationship table such as IS_USR_GP_USR is empty, it is necessary to retain the staging tables data to determine which stage miss the data in the initial place due to:

1. With REPOPULATETABLES enabled during data load, Operation is performed by purging the existing relationship tables completely and then repopulating the tables.

Refer to Knowledge Base Article for detailed explanation of the Data Load option:
KB309798: What do the <Command> entries in the EM_CONFIGURATION table refer to?
 

1. Data is deleted from the Staging tables after it is copied to the EM WH tables

Enterprise Manager moves data from the staging statistics tables to the historical statistics tables (IS_XXX_STATS)
Refer to Knowledge Base Article for detailed explanation of the Data Load option:
KB425025: Enterprise Manager Data Load Workflow in MicroStrategy 10.x and 11.x
 

ANSWER:

 
Change the value from "true" to "false" for the key "DeleteStaging" of the Enterprise Manager.
The registry path is "[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Strategy\Enterprise Manager]" in Windows operating systems. 
The "DeleteStaging" flag can be found on Linux operating systems in the MSIReg.reg file in the following section:
[HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\Enterprise Manager]
"DeleteStaging"="true"
"ExecuteInsert"="true"
"ForceSeparateDB"="false"
"HomePath"="/home/mstr/MicroStrategy/install/EnterpriseManager"
"InstallPath"="/home/mstr/MicroStrategy/install/EnterpriseManager"
"LogFilePath"="/home/mstr/MicroStrategy/install/EnterpriseManager"
"ServicePort"="9999"
"UseMultiprocess"="false"
"UseRemoteService"="true"