Book a Demo

Author Topic: Import from ODBC doesn't work for new check constraints  (Read 3502 times)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Import from ODBC doesn't work for new check constraints
« on: November 29, 2019, 11:46:59 pm »
I'm doing a database compare, and I see some new check constraints in the database that are not in EA.
After clicking "Set Import All" and "Import from ODBC", my new check constraints are not added to the model.

Doing a full ODBC import (with synchronize) does create the new check constraints

I have the same problem with updated indexes, and new unique constraints.

I'm connected to an SQL Server 2017 database using EA  v15.0.1513

Reported

Geert

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Import from ODBC doesn't work for new check constraints
« Reply #1 on: November 30, 2019, 01:32:51 am »
Are you using the ODBC driver or the SQL Server Native Client? If an ODBC driver could you try using the SQL Server Native Client?

I have this vague recollection of Sparx doing something weird with constraints, including foreign keys and check constraints, using the ODBC driver. But cannot remember the exact details.


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Import from ODBC doesn't work for new check constraints
« Reply #2 on: November 30, 2019, 03:06:33 am »
SQL Server native client 11.0

Geert