Support Article
Query used for Schema Change Tracking causes high CPU usage
SA-29909
Summary
The query which is used in the Schema Change Tracking landing page is causing high CPU usage.
Error Messages
Not applicable
Steps to Reproduce
Go to the Schema Change Tracking landing page: Designer Studio > System > Database > Schema Change Tracking.
Root Cause
The query for Schema Change Tracking was causing a full table scan.
On Postgres database, it uses information_schema view which triggers un-needed joins.
Resolution
Apply HFix-30016.
Published November 10, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.