| Thread | Last Post | Replies |
|
| SQL 2005: indexing external documents | 31 Mar 2009 01:21 GMT | 3 |
is it possible in 2005 to index documents which are not stored in the database? Or is it possible to delete the blob after indexing? Thank you
|
| Full Text Search Combinations with OR syntax! | 26 Mar 2009 17:01 GMT | 1 |
Hi all, trying to run the below search and give more weight to the location allocation of a jobsearch tool. Any ideas? Hopefully you guys can figure out what I am trying to do, very new to this so could be completely wrong. Without the "or sussex" bit added it works fine, add
|
| Treat 'ABC 123' as ("ABC" AND "123") to simplify searchwords handl | 26 Mar 2009 14:14 GMT | 1 |
Is there any syntax on the FTS that handles the input (from e.g. a client) "ABC 123" as Get all records containing both criterias. I want the same result as within SELECT * FROM myTable WHERE CONTAINS((*),' "ABC" AND "123" ') , but without having to parse the words into aphosops ...
|
| Need Full Text Search to behave LIKE '%word%' | 13 Mar 2009 17:33 GMT | 2 |
I have a few large tables in my DB and we're using LIKE '%word%' clauses so i thought i should try out full text search for perf improvements. i'm having difficulty having full text searches return a word existing
|
| Full text searching is slow | 12 Mar 2009 21:37 GMT | 2 |
Is there anything that can be done to speed up full text searches? We have a blob field that contains the contents of a document, like Word, Text, etc. It seems to take unnecessarily long to perform a full text search on this field. Would it help if we reduce it down to only ...
|
| Fulltext search via ADO.NET | 10 Mar 2009 15:46 GMT | 4 |
I have a VB.NET Windows Forms application that needs to utilize SQL Server Full text indexing to peform full text searches across many different columns. We are currently experiencing slow performance. Is there any recommendations as to speeding up the results?
|
| SQL 2000 FTS - Different results between Win2k3 and Win2000 | 03 Mar 2009 17:42 GMT | 11 |
We have a SQL 2000 server on Win2000 that returns search results that are expected, but the same search on Win2k3 returns unexpected (incorrect) data. Server 1 (returns expected results): @@version = Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
|