application of fulltext search

Hello, It is possible to search text in my blog use a query sentence instead
of several key words? Which I mean, if I want to get to know "How rich is
Bill Gates?", I can simply enter this sentence instead of enter
"Bill+Gates+rich+how" in my search textbox. If it is applicable, how?I want
to rewrite the code of my blog
Thanks, indeed
Search is unable to interpret the context of your query. English Query has
rich context sensing abilities but it works against a database.
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
"SuperRock" <moyuji@.gmail.com> wrote in message
news:eTU999zbHHA.2188@.TK2MSFTNGP04.phx.gbl...
> Hello, It is possible to search text in my blog use a query sentence
> instead of several key words? Which I mean, if I want to get to know "How
> rich is Bill Gates?", I can simply enter this sentence instead of enter
> "Bill+Gates+rich+how" in my search textbox. If it is applicable, how?I
> want to rewrite the code of my blog
> Thanks, indeed
>
|||Does your blogging solution use SQL Server as the data store? Please
elaborate (give comprehensive examples, post DDL and sample data...).
ML
http://milambda.blogspot.com/

Anyway to quick ntext Search

Helloo..
I there anyway to make ntext search faster'
I have a table of legal documents with 2 million text record, While no full
text index & search on text fields searching with "Like is very very slow".
I need anyway to make it faster using any techniques..
Do i need to use cursor or how can i solve this issue'
I can't use nvarchar coz of size limititionIslamegy wrote on Wed, 23 Nov 2005 14:18:28 +0200:

> Helloo..
> I there anyway to make ntext search faster'
> I have a table of legal documents with 2 million text record, While no
> full text index & search on text fields searching with "Like is very very
> slow". I need anyway to make it faster using any techniques..
> Do i need to use cursor or how can i solve this issue'
> I can't use nvarchar coz of size limitition
Any particular reason why you can't use Full Text Search?
Dan|||Because Full Text index dosn't apply of Text Fields of type "text",
"ntext"!!!
"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:ujyy8%23C8FHA.956@.TK2MSFTNGP10.phx.gbl...
> Islamegy wrote on Wed, 23 Nov 2005 14:18:28 +0200:
>
> Any particular reason why you can't use Full Text Search?
> Dan
>|||Islamegy wrote on Wed, 23 Nov 2005 15:27:02 +0200:

> Because Full Text index dosn't apply of Text Fields of type "text",
> "ntext"!!!
Yes it does. I'm using it on a text column in one of my databases!
Dan|||Yes, performing a non-indexed search on the text of 2 million documents is
going to be slow. I'm surprised that it's just optimization you are
concerned with and the actual feasability.
Of course, consider using the Full-Text feature.
If you must perform LIKE comparisons on the rows, perhaps it would be
possible to run a process that parses the text of each document and then
stores key words in something like a 120 length varchar column.
For example:
Jacobs;California;McNeal;disability;insu
rance;claim
Once done, this column could be used for LIKE searches.
"Islamegy" <NULL_Islamegy_NULL@.yahoo.com> wrote in message
news:OoYHFgC8FHA.1420@.TK2MSFTNGP09.phx.gbl...
> Helloo..
> I there anyway to make ntext search faster'
> I have a table of legal documents with 2 million text record, While no
> full text index & search on text fields searching with "Like is very very
> slow".
> I need anyway to make it faster using any techniques..
> Do i need to use cursor or how can i solve this issue'
> I can't use nvarchar coz of size limitition
>|||Why would you think that? It does in fact work on text and ntext columns.
Robbe Morris - 2004/2005 Microsoft MVP C#
http://www.masterado.net
"Islamegy" <NULL_Islamegy_NULL@.yahoo.com> wrote in message
news:evIRZGD8FHA.2036@.TK2MSFTNGP14.phx.gbl...
> Because Full Text index dosn't apply of Text Fields of type "text",
> "ntext"!!!
> "Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
> news:ujyy8%23C8FHA.956@.TK2MSFTNGP10.phx.gbl...
>|||How do u do it' When i try to use "Contain(Text column,"some words").. it
don't accept my query!!
As i know from my research it dosn't work on text..
Anyway my database is Arabic, so i thought ntext is ok but when i converted
it to text it became 20% faster.
Also finally i discovered that collation is work as a magic. When i switched
it from Arabic_CI_AI to Arabic_BIN this cut the search time to the half. for
now this is really so great success, if you have anyone have ideas for more
improvment plz let me now..
thanx
"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
news:%23wC2$MD8FHA.2676@.TK2MSFTNGP15.phx.gbl...
> Islamegy wrote on Wed, 23 Nov 2005 15:27:02 +0200:
>
> Yes it does. I'm using it on a text column in one of my databases!
> Dan
>|||Islamegy wrote on Wed, 23 Nov 2005 15:48:54 +0200:

> How do u do it' When i try to use "Contain(Text column,"some words").. it
> don't accept my query!!
> As i know from my research it dosn't work on text..
I'm guessing you haven't created the FTS index yet. Read BOL on how to do
this.

> Anyway my database is Arabic, so i thought ntext is ok but when i
> converted it to text it became 20% faster.
> Also finally i discovered that collation is work as a magic. When i
> switched it from Arabic_CI_AI to Arabic_BIN this cut the search time to
> the half. for now this is really so great success, if you have anyone have
> ideas for more improvment plz let me now..
Using FTS you might see a significant improvement. You'd do well to post
questions about it microsoft.public.sqlserver.fulltext
Dan|||Keep in mind that text stores text in ANSI (1 byte per character) and ntext
stores the text in Unicode (2 bytes per character) format. This is why ntext
will require more disk storage and operations on the data will be somewhat
slower. If the character set is Arabic, then you have no other choice but
the use Unicode.
"Islamegy" <NULL_Islamegy_NULL@.yahoo.com> wrote in message
news:OretoSD8FHA.1248@.TK2MSFTNGP14.phx.gbl...
> How do u do it' When i try to use "Contain(Text column,"some words").. it
> don't accept my query!!
> As i know from my research it dosn't work on text..
> Anyway my database is Arabic, so i thought ntext is ok but when i
> converted it to text it became 20% faster.
> Also finally i discovered that collation is work as a magic. When i
> switched it from Arabic_CI_AI to Arabic_BIN this cut the search time to
> the half. for now this is really so great success, if you have anyone have
> ideas for more improvment plz let me now..
> thanx
> "Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message
> news:%23wC2$MD8FHA.2676@.TK2MSFTNGP15.phx.gbl...
>

Anything new to expect with SQL Fulltext searching?

would love to see improved proximity searching, specifically the ability to find terms within x number of words of another term.

thanks-
And I'm throwing in a bit more: How about the support for various languages? Will more languages be supported?|||And how about access to the Full Text index for term frequencies?|||

Hi Andrew,

we have lots of news in the next FTS. Unfortunately, the ability to specify x number of words in NEAR is not yet sure whether it is going to make it on time for the release or not. We are aware of its importancy and working on it as we can, however, there are timelines and schedules we can not move as we would want. Be sure we will try hard to push this feature into our next release. If nto possible by then, be sure it will be in the top 5 features we address immediatelly after.

Thanks.

|||Yes. The nest FTS will include a wider range of supported languages out of the box. We are currently working on the integration of >40 new word breakers (languages). If everything goes as we expect, the next SQL Server release will have a significantly improved language coverage story in FTS.|||Yes. Our next FTS release will provide tools to access the raw data of the FTIndex by Administrators only. These tools will allow you to see the content of the FTIndex and all its metadata associated. This will be extremely useful to find answers or problems associated with your Search application. Frequency of terms will be part of the results returned by these new tools (DMVs).|||

Are the new DMVs in the current June CTP or are you saying they will be in one of the upcoming 2008 CTPs? I'm very interested in this capability for use in data mining, implementation of semantic search, etc.. On that note, are there any plans for your team to address semantic search?

|||

The new improved FTS capabilities are coming in a future CTP. As to semantic search: We are looking into semantic search capabilities, but for 2008 we only provide you the thesaurus support that is available already in SQL Server 2005 (which some improved manageability).

Best regards

Michael

|||Really excited about the inclusion new FTS features in SQL Server 2008. Did the "abililty to specify x number of words NEAR" make it into the latest beta? If not, do you think it will it be in the full version release? I am working on a project that requires this feature and am hopeful that it will become available soon.

Anything new to expect with SQL Fulltext searching?

would love to see improved proximity searching, specifically the ability to find terms within x number of words of another term.

thanks-
And I'm throwing in a bit more: How about the support for various languages? Will more languages be supported?|||And how about access to the Full Text index for term frequencies?|||

Hi Andrew,

we have lots of news in the next FTS. Unfortunately, the ability to specify x number of words in NEAR is not yet sure whether it is going to make it on time for the release or not. We are aware of its importancy and working on it as we can, however, there are timelines and schedules we can not move as we would want. Be sure we will try hard to push this feature into our next release. If nto possible by then, be sure it will be in the top 5 features we address immediatelly after.

Thanks.

|||Yes. The nest FTS will include a wider range of supported languages out of the box. We are currently working on the integration of >40 new word breakers (languages). If everything goes as we expect, the next SQL Server release will have a significantly improved language coverage story in FTS.|||Yes. Our next FTS release will provide tools to access the raw data of the FTIndex by Administrators only. These tools will allow you to see the content of the FTIndex and all its metadata associated. This will be extremely useful to find answers or problems associated with your Search application. Frequency of terms will be part of the results returned by these new tools (DMVs).|||

Are the new DMVs in the current June CTP or are you saying they will be in one of the upcoming 2008 CTPs? I'm very interested in this capability for use in data mining, implementation of semantic search, etc.. On that note, are there any plans for your team to address semantic search?

|||

The new improved FTS capabilities are coming in a future CTP. As to semantic search: We are looking into semantic search capabilities, but for 2008 we only provide you the thesaurus support that is available already in SQL Server 2005 (which some improved manageability).

Best regards

Michael

|||Really excited about the inclusion new FTS features in SQL Server 2008. Did the "abililty to specify x number of words NEAR" make it into the latest beta? If not, do you think it will it be in the full version release? I am working on a project that requires this feature and am hopeful that it will become available soon.