A client recently asked me why the Patch ERP reports did not work in Data Analytics. Upon investigating, I found that the Task Listener service was required in order for these reports to show data. Unfortunately, we chose not to enable the service because of
the dire warning about a significant increase in database size and performance impact without any explanation on how or when it should be used. This client has over 40K managed nodes on one core with a long history of patching. These reports are important to them. But they are not going to turn on this service without some understanding of what will happen, for how long, and what the overall impact will be. Some specific questions come to mind.
1. For a DB with X number of nodes, how much larger will the MP_ComputerPatchScan table get? Will it be as large as the LANDESK patchhistory table? How much growth in size should be expected?
2. Will the performance hit be permanent or only while the task listener is building the MP_ComputerPatchScan table? Other tables?
3. How long does Task Listener have to run in order to complete the inserting of records into MP_ComputerPatchScan and other tables?
4. Is there a way to monitor its progress?
5. If I chose to run it overnight or over a weekend, how can I confirm that it has completed building the MP patch tables?
If anyone has any ideas or opinions, I'd love to hear them.