I was looking to clean up the database for my ePolicy Orchestrator. When I looked at the largest tables, one stood out from the rest: SCOR_ASYNC_JOB. I was wondering what this table was for and how I might go about purging the records from the database (either in SQL directly or in ePO through a Server Task).
Also, what job or jobs might be causing the database to grow so large? When I see "async" it makes me think it has something to do with Active Directory Synchronization, but I'm not sure. I couldn't find any reference to a table by that name in the documentation.
Any help would be appreciated; Thank you for your time!
Observations from endpoints are initially entered in this table, an internal ePO task runs every few minutes to process the observations, they are then deleted from the table. When the scor_async_job table gets too large the task does not have time to finish and never deletes the rows. You will also see very high traffic on the network between ePO and the SQL server when this is happening too
You could truncate this table to regain space but they need to take machines out of observe mode if there is a ton. Or it will fill back up..
Also keep in mind you will loose all these observations also from your machines not processed if you truncate this.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.