When a foreign key constraint is removed from a SQL Server table, using the Database Diagram option and the Alter Table feature, the diagram does not reflect the update.
Consequently, when the foreign key needs to be added again, a conflict error will appear. The foreign key is stored in cache, but it's not located by doing a select * from sys.foreign_key.
The database diagram does not reflect the operation already made on it.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.