Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The following will return the name of the foreign keys in the current database that are disabled i.e. WITH NOCHECK</p> <p>For SQL Server 2005/2008:</p> <pre><code>select * from sys.foreign_keys where is_disabled=1 </code></pre> <p><br> <br></p> <p><hr> There was some discussion in the answer about the difference between disabled &amp; not trusted. What's below explains the differnce Here's some code to clarify the difference between is_disabled &amp; isnotrusted.</p> <pre><code>-- drop table t1 -- drop table t2 create table t1(i int not null, fk int not null) create table t2(i int not null) -- create primary key on t2 alter table t2 add constraint pk_1 primary key (i) -- create foriegn key on t1 alter table t1 add constraint fk_1 foreign key (fk) references t2 (i) --insert some records insert t2 values(100) insert t2 values(200) insert t2 values(300) insert t2 values(400) insert t2 values(500) insert t1 values(1,100) insert t1 values(2,100) insert t1 values(3,500) insert t1 values(4,500) ---------------------------- -- 1. enabled and trusted select name,is_disabled,is_not_trusted from sys.foreign_keys GO -- 2. disable the constraint alter table t1 NOCHECK CONSTRAINT fk_1 select name,is_disabled,is_not_trusted from sys.foreign_keys GO -- 3. re-enable constraint, data isnt checked, so not trusted. -- this means the optimizer will still have to check the column alter table t1 CHECK CONSTRAINT fk_1 select name,is_disabled,is_not_trusted from sys.foreign_keys GO --4. drop the foreign key constraint &amp; re-add -- it making sure its checked -- constraint is then enabled and trusted alter table t1 DROP CONSTRAINT fk_1 alter table t1 WITH CHECK add constraint fk_1 foreign key (fk) references t2 (i) select name,is_disabled,is_not_trusted from sys.foreign_keys GO --5. drop the foreign key constraint &amp; add but dont check -- constraint is then enabled, but not trusted alter table t1 DROP CONSTRAINT fk_1 alter table t1 WITH NOCHECK add constraint fk_1 foreign key (fk) references t2 (i) select name,is_disabled,is_not_trusted from sys.foreign_keys GO </code></pre> <p><code>is_disabled</code> means the constraint is disabled</p> <p><code>isnottrusted</code> means that SQL Server does not trust that the column has been checked against the foreign key table.</p> <p>Thus it cannot be assumed that re-enabling the foreign key constraint will be optimized. To ensure the optimizer trusts the column, it's best to drop the foreign key constraint &amp; re-create it with the <code>WITH CHECK</code> option (4.)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to list out all Foreign Keys with "WITH NOCHECK" in SQL Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNick Kavadias
    1. USNick Kavadias
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to list out all Foreign Keys with "WITH NOCHECK" in SQL Server
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSorry, I've only just read this answer. It's truly great!
      singulars
      1. PO
      1. USdigiguru
    2. COYou can re-enable the constraint and have it checked at the same time with the following code: `ALTER TABLE t1 WITH CHECK CHECK CONSTRAINT fk_1` This is a bit simpler than dropping and re-creating the constraint.
      singulars
      1. PO
      1. USAaron
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload