PerformanceCPGrowth SQL job is failing

Symptoms

The PerformanceCPGrowth SQL job errors out with message(s) like The object 'xxxxxxxx' does not exist in database 'xxxxxxxx' or is invalid for this operation. [SQLSTATE 42000] (Error 15009)

Reason

There are two potential causes:

1. Some custom tables are being created (typically by another custom SQL job) when the PerformanceCPGrowth job is running.
2. Tables belonging to a different schema than default Changepoint ones (schema=dbo) are present in a database.

Resolution

Avoid running custom jobs that overlap with Changepoint's standard ones.

Use dbo schema for your custom tables.

Alternative

Disable the PerformanceCPGrowth job if you do not need it.

This job is monitors the growth of database files and tables in case the volumes start to increase unexpectedly, so this is not something you necessarily need, especially on a test environment. It can be safely disabled, whatever the environment.