I found that with the combined CONTAINS, the plan shape for this example remained the same as the multiple-CONTAINS version. Operator costs and estimates also remained the same.<\/p>\n

For SQL Server 2005, if you had multiple CONTAINS predicates referencing columns from the same table, your execution plan would show separate remote scan operators for each reference instead of them being combined natively into a single operator.\u00a0 This behavior seems to have been addressed in recent versions, but if you have seen a variation of this issue given other conditions please share in the comments.\u00a0 Thanks!<\/p>\n","protected":false},"excerpt":{"rendered":"

The SQL Server 2005\u00a0 \u201cPerformance Tuning and Optimization (Full-Text Search)\u201d books online topic has the following recommendation: \u201cCombine multiple CONTAINS predicates into one CONTAINS predicate. In SQL Server you can specify a list of columns in the CONTAINS query.\u201d While this shows up for the SQL Server 2005 topic, there is no such statement made […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[43,28],"tags":[],"class_list":["post-1159","post","type-post","status-publish","format-standard","hentry","category-full-text-search","category-performance"],"yoast_head":"\n