Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / September 2006

Tip: Looking for answers? Try searching our database.

Still wondering

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rn - 15 Sep 2006 19:37 GMT
What was the verdict on the two ways to perform the full-text query,
contains vs. containstable?

It seemed the original poster found that containstable worked faster and
wanted to know if was essentially the same query.  The question also was
why did the containstable work faster.

It didn't seem like those two questions were really answered.  It seemed
like the original poster had found a faster way to do the query, and
then the discussion went on to why the contains method was slow and some
other workarounds.  What was wrong with the containstable method?

Should we all use constainstable instead of contains?  Is there a flaw
in the query optimizer?

Can we keep this thread going?  It seems important.
rn - 15 Sep 2006 20:14 GMT
Somehow I created a new thread by mistake.  I meant to append this to
the thread:

Performance issue with CONTAINS  
From: boblotz2001
Date Posted: 9/5/2006 2:05:00 PM
rn - 16 Sep 2006 19:56 GMT
That makes sense about the "top" parameter, but the original poster's
example did not seem to use a "top" parameter, yet achieved dramatic
performance improvement.

It seems there is still a mystery about the original poster's example
that needs to be investigated further.
Hilary Cotter - 15 Sep 2006 21:45 GMT
ContainsTable is faster than Contains because
1) it only returns two columns key and rank
2) you can limit the number of results returned by the full-text search
engine by the top_n_by_rank parameter.

If you join it against the base table without using the top_n_by_rank
parameter there are no significant performance improvements.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> What was the verdict on the two ways to perform the full-text query,
> contains vs. containstable?
[quoted text clipped - 14 lines]
>
> *** Sent via Developersdex http://www.developersdex.com ***
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.