Your underlying database has inconsistency issues... SCENARIO 1 - Count = 0

Hello all,


This is a new validation that only the Windows edition is performing at this time. We do a really simple test, namely verifying the count of database objects of certain types, or validating a specific timestamp column

SCENARIO 1 - Count = 0 (for scenario 2 please consult first reply below)



<Summary>
<ObjectType Name="DEFAULT_CONSTRAINT" Count="109" />
<ObjectType Name="FOREIGN_KEY_CONSTRAINT" Count="16" />
<ObjectType Name="PRIMARY_KEY_CONSTRAINT" Count="35" />
<ObjectType Name="SQL_TRIGGER" Count="0" />
<ObjectType Name="USER_TABLE" Count="37" />

</Summary>

It this excerpt, you can see that there areno triggers at all.


This occurs when the database has been moved using an external tool (SSMS or other), and that some options were left unchecked, which resulted in objects to be simply left behind.

It may look harsh to simply stop working when we detect this case, but our historical features, as well as the cache, depend on triggers.

The ideal scenario to recover from this is to migrate the original database again, but while ensuring that everything is duplicated.

For those that do not have access to the original database, sadly this will become an individual, heavily manual, process to fix the database.

Best regards,