It's not a default issue. Microsoft informed us that MS implements Foreign Keys differently from other databases. Thus for MS the only real solution for composite foreign keys is to replace the Foreign Key validation with triggers. Pain in the %&$#!.
MSSQL v7 appears to validate foreign keys differently from Oracle and Sybase ASA.<br>
In MSSQL if you have a table which validates both a State and City field against a City table (which includes the state) then MSSQL appears to REQUIRE you to include the City field in the update statement even...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.