Missing FK in SQL Server DDL Import

[Guillaume]

Hi,
I ran a DB import from a local SQL Server DB and noticed that FK associations between tables are missing.
Creating a DB schema in SQL Server Management Studio, I can see all associations with 3 that are missing in EA. Is this a known issue?

In my ODBC DSN, I'm using the following ODBC driver: SQL Server native client 11.0 (SQL Server is v13.0). I also ran a test with the SQL Server 10.00 driver.

[Modesto Vega]

2 obvious questions,
1) are you sure there are foreign key constraints in the database?
2) have you selected the option of reverse engineering foreign key constraints?

If the answer to both questions is yes, what version of SQL Server are you dealing with?

EA does reverse engineer FK constraints, but haven’t tried this with V15.

Edit - Could you post the DDL of a missing FK constraint?

[David Ingleton]

I am running EA v15 and have reverse engineered SQL Server databases. The foreign key constraints imported OK in my case.

[Geert Bellekens]

I also did a bunch of SQL Server reverse engineering, and in all cases I got my FK's.

Do you mean you are only missing 3 and a bunch of others imported just fine? Or are you missing all FK's.

Geert

[Guillaume]

Thank you for your replies. It appears that the DBA found some mistakes in the delivered schema so I'm waiting for a new file to test. Hopefully it will sort the few missing FK that I found, and confirming that it's not related with EA