Hello,
Can anybody explain me why is it showing rank as 0 always in the result?
Table Data:
LLBPSEPG
This is test for the Search
search test for heat
mango apple banana
eating banana is good for health
man eats rice healthy
big laod in the ship hot
SPEG App LLBP - Next LLBP
Lesson learned are from mistakes
good apples are tasty dry
mangos are too costly dried
it is time for starting the project
Query:
SELECT LLBPSEPG
FROM T_TM_LLBPData a, FREETEXTTABLE(T_TM_LLBPData, LLBPSEPG, 'apple banana
mango ') b
WHERE a.LLBPNo = b.[key]
Output:
LLBPSEPG Rank
mangos are too costly dried 0
eating banana is good for health 0
mango apple banana 0
good apples are tasty dry 0
thanks and regards
SathianSathian,
Is the text below "Table data" and for column "LLBPSEPG" the actual text and
number of rows (1) in your table "T_TM_LLBPData"? If so, then this is too
small a table to get correct RANK values. Specifically, RANK requires a
statistically significant number of rows (usually >10,000) and a
corresponding number of unique non-noise words to get correct RANK values
returned. See SQL Server 2000 BOL title "Full-text Search Recommendations"
for more information on RANK. Additionally, your FREETEXTTABLE query is
searching for the phrase "apple banana mango" and while no one row has this
exact phrase, you did get results for variations of these words including
"apples" for your query specifying "apple". You might want to try searching
on the phrase "mango apple banana" as there is an exact match for this
phrase in your small table's data.
Hope that helps!
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Sathian T" <sathian.t@.in.Bosch.com> wrote in message
news:cufqjk$g8h$1@.ns2.fe.internet.bosch.com...
> Hello,
> Can anybody explain me why is it showing rank as 0 always in the result?
>
> Table Data:
> LLBPSEPG
> This is test for the Search
> search test for heat
> mango apple banana
> eating banana is good for health
> man eats rice healthy
> big laod in the ship hot
> SPEG App LLBP - Next LLBP
> Lesson learned are from mistakes
> good apples are tasty dry
> mangos are too costly dried
> it is time for starting the project
>
> Query:
> SELECT LLBPSEPG
> FROM T_TM_LLBPData a, FREETEXTTABLE(T_TM_LLBPData, LLBPSEPG, 'apple banana
> mango ') b
> WHERE a.LLBPNo = b.[key]
> Output:
> LLBPSEPG Rank
> mangos are too costly dried 0
> eating banana is good for health 0
> mango apple banana 0
> good apples are tasty dry 0
>
> thanks and regards
> Sathian
>
>|||Dear Friends,
Do any of you have an answer for this?
Regards
Sathian|||Sathian,
Is the text below "Table data" and for column "LLBPSEPG" the actual text and
number of rows (1) in your table "T_TM_LLBPData"? If so, then this is too
small a table to get correct RANK values. Specifically, RANK requires a
statistically significant number of rows (usually >10,000) and a
corresponding number of unique non-noise words to get correct RANK values
returned. See SQL Server 2000 BOL title "Full-text Search Recommendations"
for more information on RANK. Additionally, your FREETEXTTABLE query is
searching for the phrase "apple banana mango" and while no one row has this
exact phrase, you did get results for variations of these words including
"apples" for your query specifying "apple". You might want to try searching
on the phrase "mango apple banana" as there is an exact match for this
phrase in your small table's data.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Sathian T" <sathian.t@.in.Bosch.com> wrote in message
news:cv18fk$bqn$1@.ns2.fe.internet.bosch.com...
> Dear Friends,
> Do any of you have an answer for this?
> Regards
> Sathian
>
>
2012年3月21日星期三
Full text query contained only ignored words
Hello All,
Please explain this Fulltext behavior to me.
We have an asp application that is using sql that returns the above error
when you search for the word can't. If you search for "don't" or "Doesn't"
or pretty much anything else with an apostrophe, results are returned.
The same thing happens when you search for a decimal number. If I search
for 4.0, I get the above error. If I search for 4.00.0 I will get results.
Thanks in advance!
Jake
"GitarJake" <spamaintme@.oz.net> wrote in message
news:C0vRe.101151$Ep.81169@.lakeread02...
> Hello All,
> Please explain this Fulltext behavior to me.
> We have an asp application that is using sql that returns the above error
> when you search for the word can't. If you search for "don't" or
> "Doesn't" or pretty much anything else with an apostrophe, results are
> returned.
> The same thing happens when you search for a decimal number. If I search
> for 4.0, I get the above error. If I search for 4.00.0 I will get
> results.
Check the noise.X file in your FTDATA\Config folder (where X is the
extension related to your word breaker language - eng for English, enu for
US English, etc).
4 is in the list. I'm guessing that when 4.0 is passed FTS treats it a
number and so finds it in the noise word file, whereas when 4.00.0 is used
it's obviously not a number and so does a search for it as is.
Can is a word in the noise word list too. I'm guessing FTS splits can't into
can and not internally, and errors because can is in the list.
What you could do is empty the noise word file - leave only a single line in
it with a single space on it. Then run a full population. This has the
effect of not erroring on any words (although some characters that are used
as word breakers will still throw the noise words error, you'll have to
filter these out in your query builder).
Dan
|||You might want to review the following
http://www.indexserverfaq.com/noise.htm
Hilary Cotter
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
"GitarJake" <spamaintme@.oz.net> wrote in message
news:C0vRe.101151$Ep.81169@.lakeread02...
> Hello All,
> Please explain this Fulltext behavior to me.
> We have an asp application that is using sql that returns the above error
> when you search for the word can't. If you search for "don't" or
"Doesn't"
> or pretty much anything else with an apostrophe, results are returned.
> The same thing happens when you search for a decimal number. If I search
> for 4.0, I get the above error. If I search for 4.00.0 I will get
results.
>
> Thanks in advance!
> Jake
>
|||Hi Daniel,
Thanks for responding.
I have removed "can" from both the fulltext noise.enu word list in
ftdata\config; and the Indexing noise.enu. The wordbreaker in FTI is
neutral. I completely deleted the FT catalogs and manually recreated and
repopulated them. The results were the same.
Then I deleted the contents FTI's noise.enu except for a space and now, the
search simply does not return results. It seems like I can search for the
word can't on any other search engine but ours. Below is the query we are
passing using just the word *can't*. Can you tell if there is anything
within the query that might be better able to produce results?
select ARTICLE_ID, ARTICLE_STITLE, ARTICLE_LTITLE, ARTICLE_SUMMARY
,ARTICLE_STATUS, ARTICLE_APPROVED, DEPART_REF, USER_REF_OWNER,
USER_REF_EDITOR, ARTICLE_REVIEW_DATE, ARTICLE_EXPIRE, RANK,
PUBLIC_DIVISION_REF From ARTICLES as A, containstable(ARTICLES, *, '
"can''t" ') as AST where (LANGUAGE_REF= 1 and ARTICLE_DISABLE_SEARCH <> 1 )
and AST.[KEY] = A.ARTICLE_ID order by RANK desc
MIS query: "can''t"
TIA
Jake
"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:%23BYyg8vrFHA.3096@.TK2MSFTNGP15.phx.gbl...
> "GitarJake" <spamaintme@.oz.net> wrote in message
> news:C0vRe.101151$Ep.81169@.lakeread02...
> Check the noise.X file in your FTDATA\Config folder (where X is the
> extension related to your word breaker language - eng for English, enu for
> US English, etc).
> 4 is in the list. I'm guessing that when 4.0 is passed FTS treats it a
> number and so finds it in the noise word file, whereas when 4.00.0 is used
> it's obviously not a number and so does a search for it as is.
> Can is a word in the noise word list too. I'm guessing FTS splits can't
> into can and not internally, and errors because can is in the list.
> What you could do is empty the noise word file - leave only a single line
> in it with a single space on it. Then run a full population. This has the
> effect of not erroring on any words (although some characters that are
> used as word breakers will still throw the noise words error, you'll have
> to filter these out in your query builder).
> Dan
>
|||To test this I added "Can't you see?" to the end of a book title in the pubs
database. I then created a new catalog on the title column, ran a full
population, and then ran this:
select * from titles where contains(title,'can''t')
and up popped the row I'd added the phrase to. I then tried this:
select a.* from titles a ,containstable(titles,*,'can''t') b where
a.title_id = b.[key]
select a.* from titles a ,containstable(titles,*,'"can''t"') b where
a.title_id = b.[key]
and again, I get the same row back from both versions. So it's not a problem
with the apostrophe, nor an issue with the double quotes.
The only other thing in your query that will prevent the row from appearing
will be if ARTICLE_DISABLE_SEARCH = 1 or LANGUAGE_REF <> 1. Have you tried
running the query with these clauses removed just in case?
Dan
GitarJake wrote on Sun, 4 Sep 2005 12:33:07 -0400:
[vbcol=seagreen]
> Hi Daniel,
> Thanks for responding.
> I have removed "can" from both the fulltext noise.enu word list in
> ftdata\config; and the Indexing noise.enu. The wordbreaker in FTI is
> neutral. I completely deleted the FT catalogs and manually recreated and
> repopulated them. The results were the same.
> Then I deleted the contents FTI's noise.enu except for a space and now,
> the search simply does not return results. It seems like I can search for
> the word can't on any other search engine but ours. Below is the query we
> are passing using just the word *can't*. Can you tell if there is
> anything within the query that might be better able to produce results?
> select ARTICLE_ID, ARTICLE_STITLE, ARTICLE_LTITLE, ARTICLE_SUMMARY
> ,ARTICLE_STATUS, ARTICLE_APPROVED, DEPART_REF, USER_REF_OWNER,
> USER_REF_EDITOR, ARTICLE_REVIEW_DATE, ARTICLE_EXPIRE, RANK,
> PUBLIC_DIVISION_REF From ARTICLES as A, containstable(ARTICLES, *, '
> "can''t" ') as AST where (LANGUAGE_REF= 1 and ARTICLE_DISABLE_SEARCH <>
> 1 ) and AST.[KEY] = A.ARTICLE_ID order by RANK desc
> MIS query: "can''t"
> TIA
> Jake
> "Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message news:%23BYyg8vrFHA.3096@.TK2MSFTNGP15.phx.gbl...
Please explain this Fulltext behavior to me.
We have an asp application that is using sql that returns the above error
when you search for the word can't. If you search for "don't" or "Doesn't"
or pretty much anything else with an apostrophe, results are returned.
The same thing happens when you search for a decimal number. If I search
for 4.0, I get the above error. If I search for 4.00.0 I will get results.
Thanks in advance!
Jake
"GitarJake" <spamaintme@.oz.net> wrote in message
news:C0vRe.101151$Ep.81169@.lakeread02...
> Hello All,
> Please explain this Fulltext behavior to me.
> We have an asp application that is using sql that returns the above error
> when you search for the word can't. If you search for "don't" or
> "Doesn't" or pretty much anything else with an apostrophe, results are
> returned.
> The same thing happens when you search for a decimal number. If I search
> for 4.0, I get the above error. If I search for 4.00.0 I will get
> results.
Check the noise.X file in your FTDATA\Config folder (where X is the
extension related to your word breaker language - eng for English, enu for
US English, etc).
4 is in the list. I'm guessing that when 4.0 is passed FTS treats it a
number and so finds it in the noise word file, whereas when 4.00.0 is used
it's obviously not a number and so does a search for it as is.
Can is a word in the noise word list too. I'm guessing FTS splits can't into
can and not internally, and errors because can is in the list.
What you could do is empty the noise word file - leave only a single line in
it with a single space on it. Then run a full population. This has the
effect of not erroring on any words (although some characters that are used
as word breakers will still throw the noise words error, you'll have to
filter these out in your query builder).
Dan
|||You might want to review the following
http://www.indexserverfaq.com/noise.htm
Hilary Cotter
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
"GitarJake" <spamaintme@.oz.net> wrote in message
news:C0vRe.101151$Ep.81169@.lakeread02...
> Hello All,
> Please explain this Fulltext behavior to me.
> We have an asp application that is using sql that returns the above error
> when you search for the word can't. If you search for "don't" or
"Doesn't"
> or pretty much anything else with an apostrophe, results are returned.
> The same thing happens when you search for a decimal number. If I search
> for 4.0, I get the above error. If I search for 4.00.0 I will get
results.
>
> Thanks in advance!
> Jake
>
|||Hi Daniel,
Thanks for responding.
I have removed "can" from both the fulltext noise.enu word list in
ftdata\config; and the Indexing noise.enu. The wordbreaker in FTI is
neutral. I completely deleted the FT catalogs and manually recreated and
repopulated them. The results were the same.
Then I deleted the contents FTI's noise.enu except for a space and now, the
search simply does not return results. It seems like I can search for the
word can't on any other search engine but ours. Below is the query we are
passing using just the word *can't*. Can you tell if there is anything
within the query that might be better able to produce results?
select ARTICLE_ID, ARTICLE_STITLE, ARTICLE_LTITLE, ARTICLE_SUMMARY
,ARTICLE_STATUS, ARTICLE_APPROVED, DEPART_REF, USER_REF_OWNER,
USER_REF_EDITOR, ARTICLE_REVIEW_DATE, ARTICLE_EXPIRE, RANK,
PUBLIC_DIVISION_REF From ARTICLES as A, containstable(ARTICLES, *, '
"can''t" ') as AST where (LANGUAGE_REF= 1 and ARTICLE_DISABLE_SEARCH <> 1 )
and AST.[KEY] = A.ARTICLE_ID order by RANK desc
MIS query: "can''t"
TIA
Jake
"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:%23BYyg8vrFHA.3096@.TK2MSFTNGP15.phx.gbl...
> "GitarJake" <spamaintme@.oz.net> wrote in message
> news:C0vRe.101151$Ep.81169@.lakeread02...
> Check the noise.X file in your FTDATA\Config folder (where X is the
> extension related to your word breaker language - eng for English, enu for
> US English, etc).
> 4 is in the list. I'm guessing that when 4.0 is passed FTS treats it a
> number and so finds it in the noise word file, whereas when 4.00.0 is used
> it's obviously not a number and so does a search for it as is.
> Can is a word in the noise word list too. I'm guessing FTS splits can't
> into can and not internally, and errors because can is in the list.
> What you could do is empty the noise word file - leave only a single line
> in it with a single space on it. Then run a full population. This has the
> effect of not erroring on any words (although some characters that are
> used as word breakers will still throw the noise words error, you'll have
> to filter these out in your query builder).
> Dan
>
|||To test this I added "Can't you see?" to the end of a book title in the pubs
database. I then created a new catalog on the title column, ran a full
population, and then ran this:
select * from titles where contains(title,'can''t')
and up popped the row I'd added the phrase to. I then tried this:
select a.* from titles a ,containstable(titles,*,'can''t') b where
a.title_id = b.[key]
select a.* from titles a ,containstable(titles,*,'"can''t"') b where
a.title_id = b.[key]
and again, I get the same row back from both versions. So it's not a problem
with the apostrophe, nor an issue with the double quotes.
The only other thing in your query that will prevent the row from appearing
will be if ARTICLE_DISABLE_SEARCH = 1 or LANGUAGE_REF <> 1. Have you tried
running the query with these clauses removed just in case?
Dan
GitarJake wrote on Sun, 4 Sep 2005 12:33:07 -0400:
[vbcol=seagreen]
> Hi Daniel,
> Thanks for responding.
> I have removed "can" from both the fulltext noise.enu word list in
> ftdata\config; and the Indexing noise.enu. The wordbreaker in FTI is
> neutral. I completely deleted the FT catalogs and manually recreated and
> repopulated them. The results were the same.
> Then I deleted the contents FTI's noise.enu except for a space and now,
> the search simply does not return results. It seems like I can search for
> the word can't on any other search engine but ours. Below is the query we
> are passing using just the word *can't*. Can you tell if there is
> anything within the query that might be better able to produce results?
> select ARTICLE_ID, ARTICLE_STITLE, ARTICLE_LTITLE, ARTICLE_SUMMARY
> ,ARTICLE_STATUS, ARTICLE_APPROVED, DEPART_REF, USER_REF_OWNER,
> USER_REF_EDITOR, ARTICLE_REVIEW_DATE, ARTICLE_EXPIRE, RANK,
> PUBLIC_DIVISION_REF From ARTICLES as A, containstable(ARTICLES, *, '
> "can''t" ') as AST where (LANGUAGE_REF= 1 and ARTICLE_DISABLE_SEARCH <>
> 1 ) and AST.[KEY] = A.ARTICLE_ID order by RANK desc
> MIS query: "can''t"
> TIA
> Jake
> "Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message news:%23BYyg8vrFHA.3096@.TK2MSFTNGP15.phx.gbl...
Full text Problems
Hi all, my english is very bad, so i try to explain...
when i put the string
and Contains (PG.GenericTitleFullTxt,'"* Dias *" AND "* que *"AND "* Abalaram *" AND "* Mundo * "')
in my query, the results show up.... but is only i put the " * O * " in the search string and not shows ..something linke
and Contains (PG.GenericTitleFullTxt,'"* Dias *" AND "* que *"AND "* Abalaram *" AND "* O * " AND * Mundo * "')
All the conditions for the "and" exists....in my catalog i have the string
Dias que Abalaram O Mundo
many times..bu if i put the "O" in the search ...not shows nothing...
I droped the catalog, indexes..rebuild..etc...
Anyone can help me ?
Thanks..
First of all, you should leave the blank before and after the words, as the word breaker has already broken the words in the database to small pieces which can be recognized. if the words you are searching for are all single words you should also leave the * signs due to the same reasons mentioned above.Jens K. Suessmeyer
http://www.sqlserver2005.de
2012年3月9日星期五
Full text help.. anyone?
Can anyone explain me how to configure full text to run on
a windows 2003 cluster (2 machines 1 sql node)?
Claudia,
Sorry for the late reply, however, assuming you're installing SQL Server
2000 Enterprise Edition on Windows 2003 Advance or Enterprise servers, Full
Text Search is installed by default. If you're using SQL Server 7.0, then
Full-Text Search is not supported in a clustered environment. Without more
info on what you're looking for, a series of steps, or troubleshooting a
specific error, it's kinda hard to provide relevant info. However, the below
KB articles should give you a good starting point...
KB Articles:
817301 PRB: Microsoft Search Full-Text Catalog Population Fails When You
Upgrade SQL Server 2000 Failover Cluster to SQL Server 2000 Service Pack 3
http://support.microsoft.com/default...&Product=sql2k
812666 How to recover a failed full-text search resource on a clustered
instance of SQL Server 2000
http://support.microsoft.com/default...&Product=sql2k
304282 (Q304282) PRB: Full Text Resource Fails to Come Online on a Cluster
with "Event ID 1069 :SQL Cluster Resource 'Full Text' failed" Error Message
http://support.microsoft.com/default...&Product=sql2k
296890 (Q296890) PRB: SQL Server 2000 Fails to Install on a Cluster If
Service Startup Account Contains a Space
http://support.microsoft.com/default...&Product=sql2k
810056 INF: You Must Use Resource-Specific Registry Keys for SQL Server
Cluster Resources
http://support.microsoft.com/default...&Product=sql2k
295732 INF: Creating Databases or Changing Disk File Locations on a Shared
Cluster Drive on Which SQL Server 2000 was not Originally Installed
http://support.microsoft.com/default...&Product=sql2k
260758 INF: Frequently Asked Questions - SQL Server 2000 - Failover
Clustering
http://support.microsoft.com/default...&Product=sql2k
814035 FIX: A Full-Text Population Fails After You Apply SQL Server 2000
Service Pack 3
http://support.microsoft.com/default...&Product=sql2k
811168 INF: SQL Server 2000 Service Pack 3 or Service Pack 3a
Pre-Installation Checklist for SQL Server 2000 Virtual Server for Failover
Clustering
http://support.microsoft.com/default...&Product=sql2k
243218 Installation order for SQL Server 2000 Enterprise Edition on
Microsoft Cluster Server
http://support.microsoft.com/default...&Product=sql2k
Regards,
John
"Claudia" <anonymous@.discussions.microsoft.com> wrote in message
news:2fbc101c46da9$5bedfac0$a401280a@.phx.gbl...
> Can anyone explain me how to configure full text to run on
> a windows 2003 cluster (2 machines 1 sql node)?
>
a windows 2003 cluster (2 machines 1 sql node)?
Claudia,
Sorry for the late reply, however, assuming you're installing SQL Server
2000 Enterprise Edition on Windows 2003 Advance or Enterprise servers, Full
Text Search is installed by default. If you're using SQL Server 7.0, then
Full-Text Search is not supported in a clustered environment. Without more
info on what you're looking for, a series of steps, or troubleshooting a
specific error, it's kinda hard to provide relevant info. However, the below
KB articles should give you a good starting point...
KB Articles:
817301 PRB: Microsoft Search Full-Text Catalog Population Fails When You
Upgrade SQL Server 2000 Failover Cluster to SQL Server 2000 Service Pack 3
http://support.microsoft.com/default...&Product=sql2k
812666 How to recover a failed full-text search resource on a clustered
instance of SQL Server 2000
http://support.microsoft.com/default...&Product=sql2k
304282 (Q304282) PRB: Full Text Resource Fails to Come Online on a Cluster
with "Event ID 1069 :SQL Cluster Resource 'Full Text' failed" Error Message
http://support.microsoft.com/default...&Product=sql2k
296890 (Q296890) PRB: SQL Server 2000 Fails to Install on a Cluster If
Service Startup Account Contains a Space
http://support.microsoft.com/default...&Product=sql2k
810056 INF: You Must Use Resource-Specific Registry Keys for SQL Server
Cluster Resources
http://support.microsoft.com/default...&Product=sql2k
295732 INF: Creating Databases or Changing Disk File Locations on a Shared
Cluster Drive on Which SQL Server 2000 was not Originally Installed
http://support.microsoft.com/default...&Product=sql2k
260758 INF: Frequently Asked Questions - SQL Server 2000 - Failover
Clustering
http://support.microsoft.com/default...&Product=sql2k
814035 FIX: A Full-Text Population Fails After You Apply SQL Server 2000
Service Pack 3
http://support.microsoft.com/default...&Product=sql2k
811168 INF: SQL Server 2000 Service Pack 3 or Service Pack 3a
Pre-Installation Checklist for SQL Server 2000 Virtual Server for Failover
Clustering
http://support.microsoft.com/default...&Product=sql2k
243218 Installation order for SQL Server 2000 Enterprise Edition on
Microsoft Cluster Server
http://support.microsoft.com/default...&Product=sql2k
Regards,
John
"Claudia" <anonymous@.discussions.microsoft.com> wrote in message
news:2fbc101c46da9$5bedfac0$a401280a@.phx.gbl...
> Can anyone explain me how to configure full text to run on
> a windows 2003 cluster (2 machines 1 sql node)?
>
订阅：
博文 (Atom)