The EPO_EVENT_AUTO_ID field, in the SCOR_EVENTS table of the ePO database, is missing the cascade option. The cascade option can't be applied because an FK constraint is present on the field.
To view the constraint, run the following command against the ePO database:
SELECT
f.name AS foreign_key_name
,OBJECT_NAME(f.parent_object_id) AS table_name
,COL_NAME(fc.parent_object_id, fc.parent_column_id) AS
constraint_column_name
,OBJECT_NAME (f.referenced_object_id) AS referenced_object
,COL_NAME(fc.referenced_object_id, fc.referenced_column_id) AS referenced_column_name
,is_disabled
,delete_referential_action_desc
,update_referential_action_desc
FROM sys.foreign_keys AS f
INNER JOIN sys.foreign_key_columns AS fc
ON f.object_id = fc.constraint_object_id
WHERE f.parent_object_id = OBJECT_ID('scor_events');
Appropriate output is similar to the example below:
foreign_key_name |
table_name |
constraint_column_name |
referenced_object |
referenced_column_name |
is_disabled |
delete_referential_action_desc |
update_referential_action_desc |
SCOR_EVENTS_EPO_EVENTS |
SCOR_EVENTS |
EPO_EVENT_AUTO_ID |
EPOEventsMT |
AutoID |
0 |
CASCADE |
CASCADE |