THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Tibor Karaszi

Non-trusted constraints and performance

This blog has moved! You can find this content at the following new location:

Published Saturday, January 12, 2008 6:09 PM by TiborKaraszi

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Alejandro Mesa said:

Hi Tibor,

It was interesting reading the second part of this blog.

One example I use to talk about the impact of having non-trusted constraints is when working with partitioned views. If one of the tables participating in the partitioned view, has a non-trusted check constraints (constraint defining the partition), the optimizer will have to carry the operation in all tables partiticipating in the view.

Looking forward to your next blog,


January 13, 2008 8:17 PM

TiborKaraszi said:

Hi again Alejandro,

Yes, another good example where non-trusted constraint can hurt you. Thanks. :-)

January 14, 2008 1:22 PM

ALZDBA said:

Another reason for a constraint to be considered non-trusted is if you create it using the "not for replication" clause !

I just figured that out the hard way because some FK constraints weren't considered trusted and the with check check constraint didn't  resolve the issue. (sql2005/sql2008 sp1)

May 3, 2010 8:28 AM

Journey said:

a good example,is good for us .thank you

August 8, 2012 3:11 AM

Leave a Comment

Privacy Statement