| Thread | Last Post | Replies |
|
| CONTAINS on sql2005 | 24 Feb 2006 11:15 GMT | 2 |
I've just discovered that the CONTAINS clause on sql2005 can search multiple columns - great! Is there a way to return which column the search word(s) were found in? Dunc
|
| Full-Text options disabled in management console | 23 Feb 2006 22:49 GMT | 4 |
If I open a SQL 2000 database using the management console the Full-Text options are grayed-out / disabled...even though Full-Text search service is started and I can create full-text catalogs using stored procedures in QA and search using those catalog in QA. This problem ...
|
| Problem with Multilanguage and escape characters | 23 Feb 2006 16:56 GMT | 6 |
I have a problem with a request concerning chineese data on a nText field... Here is a sample: TABLE : T FIELD : TXT as nText
|
| Optimize queries | 23 Feb 2006 12:26 GMT | 1 |
We have a SQL-Server 2000 DB with Full-Text-Search enabled on some of the tables. We have one table with about 15 million records. The table looks like
|
| Enabling Fulltext Service on database | 23 Feb 2006 12:26 GMT | 1 |
one of my customers moved a SQL Database from one server to another. The database had 2 fulltext catalogs associated. On the new DB Server the fulltext service doesn't start using sp_fulltext_database 'enable'.
|
| Hidden Ignored Words? | 23 Feb 2006 02:09 GMT | 5 |
We are getting the dreaded "A clause of the query contained only ignored words." error when a user searches for the following term: "3.0" (without quotes). I've checked all the noise word lists and "3.0" is not in there. "3" is
|
| Full-text Search | 21 Feb 2006 17:35 GMT | 2 |
Hello, I have a full-text enabled field in my table has the following content as an example: "SQL Server is a comprehensive, integrated, end-to-end data solution that empowers your people by providing a more secure, reliable, and
|
| Does SQL2005 still require all FTI keywords to match in the same column? | 20 Feb 2006 18:56 GMT | 3 |
My understanding of full-text index searching is that CONTAINS() requires that all the keywords supplied (separated by AND) must match in the same column in order for the record to be considered a match and returned. So if we have a situation where we need keywords to match in
|
| Rather empty gatherer logs | 17 Feb 2006 09:28 GMT | 4 |
I noticed that we were getting no results in our search this morning. The records were in the DB, search terms matched when using "LIKE" but not CONTAINS. Once I did a repopulation (incremental) all worked fine. What I don't understand is that the repopulation is actually scheduled
|
| full-text queries with express edition | 14 Feb 2006 09:15 GMT | 2 |
I understand that full-text indexing is not available in the express edition. My situation is that we have to write an application to take advantage of full-text-indexing when available.
|
| Full-text enabled greyed out | 10 Feb 2006 23:23 GMT | 10 |
I have Windows Server 2003 for Small Business Server. I am trying to make the full-text searches work with Sharepoint. I initially didn't have MSSearch installed so I went ahead and started the install for SQL Server 2000 and selected the sharepoint instance of the database (which
|
| search within single xml document in SQL 2005 | 10 Feb 2006 20:08 GMT | 9 |
I have a full text indexed xml column in sql server 2005 containing the following xml snippet: <plays> <folder id="681">
|
| FiltDump.exe Errors | 10 Feb 2006 14:50 GMT | 3 |
I cannot get Filtdump.exe to run. I have a server where MS SQL FullText search is working perfectly (PDF, Office, HTML etc.) but when I run FiltDump.exe on one of the PDFs I the following message: C:\>temp\Filtdump.exe test.pdf
|
| "ImpersonateClient" property in Yukon | 10 Feb 2006 13:25 GMT | 1 |
Does anybody knows how to get the value for "ImpersonateClient" property which is on IntegratedSecurity Object in SQL - DMO for SQL Server 2005 (Yukon). Documentation says that the functionality has been moved to "Server
|
| a question or two re fulltext queries | 09 Feb 2006 20:10 GMT | 5 |
i'm using SQL Server 2000 (SP3, I think). i am looking at SQL for finding documents (table DOC) based on a couple of criteria, one of which involves a fulltext index on a related table (TXT). i discovered today that a less selective CONTAINS() clause:
|