Skip to main content
Question

An explicit DROP INDEX is not allowed on index 'dbo.table.unique_object'. It is being used for FOREIGN KEY constraint enforcement.

  • November 18, 2025
  • 0 replies
  • 6 views

SanderAdam
Captain
Forum|alt.badge.img+5

Hello everyone,

As the title suggests I have the that error on indexes:

I did see a post where a validation is supposed to be in place to prevent this from happening. But does that also count for when you create a unique constraint on multiple primary keys? Because I cannot find the validation and now I cannot (re)build my database anymore. I would need to fix this first, but in the newest validations by Thinkwise, a validation on this table would pop up urging it needs a unique constraint on the two primary keys used in the constraint. So what can I do to fix this? Did anybody else experience this problem?

 

0 replies

Be the first to reply!