| Thread | Last Post | Replies |
|
| Scheduled population not starting. Please help!! | 31 Oct 2006 20:13 GMT | 1 |
I'm at my wits end. I have set up both a full & incremental schedule on a table that has an full-text index on one of its fields. Problem is though - its not starting
|
| How to force FTS on fractions? | 30 Oct 2006 16:08 GMT | 1 |
When I made the jump to SQL 2005 from SQL 2000, the following query stopped working. ie no result set unless I remove the fraction 1/4. (Removing the fraction 1/4 works, but then returns many many rows) SELECT * FROM MAKT
|
| SQL to see what documents are supported? | 26 Oct 2006 17:08 GMT | 2 |
I once had some SQL to see what document types are supported by Full Text Search that worked at least for SQL2005 and lost it. Can somebody post that again please? Would be nice to have for SQL2000 if it is possible also.
|
| Remove from noise list | 26 Oct 2006 15:20 GMT | 1 |
how I can remove "c" from my noise word and how I rebuilt my catalog to search on c#, c+, and c.
|
| search for words with punctuation - IE 319.109.092 | 23 Oct 2006 09:59 GMT | 2 |
We are using FTS in our search to get a performance boost over a traditional LIKE search. It is working really well, but there is one issue. We would like to index and search for text that look like
|
| Problem with full text search | 20 Oct 2006 16:10 GMT | 3 |
First of all sorry for my poor english.... I write from Italy... I'm using full-text search with SQL Express 2005 and I can't undestand a lot... This is the situation:
|
| No search results for 1 only table | 20 Oct 2006 14:35 GMT | 3 |
I have spent hours on this problem and I can not even find where to start. I have full-text enabled on 15 our of about 100 tables in my database. This copy of the database has been running for about 4 months. Everything was working fine except that search has stopped
|
| Is this possible with Full Text Indexing? | 19 Oct 2006 20:33 GMT | 2 |
(SQL Server 2000, SP4) Hello all! I am wrestling with a problem that I hope someone can help me with. I have a series of related tables (fairly normalized), each of which has a textual
|
| sp_fulltext_catalog | 17 Oct 2006 10:22 GMT | 1 |
In 1 database I have 2 cataolg files. how many times a day I must execute sp_fulltext_catalog sp? "Full" or "incremental" which type of arguments I must use? and how many times ?(a day or a week)
|
| Text or VarChar fields | 17 Oct 2006 00:38 GMT | 5 |
I have a table that has some VarChar(8000) fields in it. I have run into problems with records having more than 4000 chars in each of the fields which gives me an error saying that the record size too large ( > 8060).
|
| Scripting Full Text Index | 16 Oct 2006 21:05 GMT | 2 |
I'm using SQL Server 2005 and was just wondering if its possible to get the values set for full text indexing via I was just wondering if it is possible to script the full text indexes setup from the Management Studio (in a similar way as you can for db
|
| Fulltext Query Cost | 12 Oct 2006 04:42 GMT | 2 |
I have a query which have fulltext search. The query cost of this query is around 3-4 only (Show in Execution Plan). I am using ASP calling VBCOM adodb way to execute this query. Why I always hit timeout for the first search (using Machine A). There is no timeout after that. ...
|
| Maximum FT Catalogs per server | 11 Oct 2006 15:41 GMT | 3 |
Hello, I am trying to see what the limit is on creating FT catalogs per server. I have found 2 Non MS links stating 256 catalogs per server, but I really need to confirm this. Thanks for your help
|
| Different result when using Indexing Service Query Form and SQL Server | 11 Oct 2006 15:24 GMT | 3 |
When I use the "Indexing Service Query Form", searching documents for the word "Désiré", I get 50 matched records. If I run the following query from SQL-Server 2005 (on the same machine)
|
| what does "NEAR" operator mean? | 10 Oct 2006 17:47 GMT | 3 |
What exactly does the "NEAR" operator mean in fulltext search query? I searched the online book and could only find the following info: "Indicates that the word or phrase on the left side of the NEAR or ~ operator should be approximately close to the word or phrase on the right
|