This script reports table columns that are not foreign keys but that have the same name and type as columns that are part of clustered or unique non-clustered indexes, making them candidates for adding a FOREIGN KEY constraint.
Because there may be cases in which columns in different tables have the same name and type but are in fact unrelated, it is impossible to know for certain whether the candidate columns should be foreign keys. That’s why they’re only candidates. Use the results of the script to decide whether they are or not.
You can use the output of this script to decide whether the definition of the candidate columns could be changed to enforce a FOREIGN KEY constraint. By enforcing FOREIGN KEY constraints, you can help ensure data integrity.
To use the script, simply execute it against a target database.