You could probably improve performance a little by using CHARINDEX(TableName,Definition,0)>0 instead of CHARINDEX(TableName,Definition,0)<>0. CharIndex would never be negative, right?, so > would be more efficient than <>. If...