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 / December 2006

Tip: Looking for answers? Try searching our database.

SQL Server Freetext Error: Your Search Produced to many results

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Neil A - 05 Oct 2006 10:41 GMT
Hi,

I have an SQL Server 2000 Std installation with a full text cat on a large
table containing 2-3m rows.

When querying on particular words/phrases SQL Server reports too many results.

Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E14)
[Microsoft][ODBC SQL Server Driver][SQL Server]Your search generated too
many results. Please perform a more specific search.

Can anyone help with explaining this issue?
what the limits are?

Thanks

Neil

Thanks
Hilary Cotter - 05 Oct 2006 13:38 GMT
Can I see your query?

I think you might want to use the top_n_by_rank parameter in containstable
to limit your result set to something smaller.

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

> Hi,
>
[quoted text clipped - 17 lines]
>
> Thanks
Roopali Kaujalgi - 09 Dec 2006 00:58 GMT
In addition to the suggestion made in the previous post, you could also try
the following depending on your query.
If you are using prefix query make the prefix more specific, query on lesser
columns or make the common word a noise word.

> Can I see your query?
>
[quoted text clipped - 22 lines]
> >
> > Thanks
 
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.