Question about Proximity (NEARness) with Full Text Indexing on SQL Server 7

Hello group,
Does anyone know how near a word needs to be to another word to be
included in the results of a CONTAINS search that uses NEAR? Is this
setting adjustable? Is is stored in the registry? INI or config file?
I'm using SQL Server 7 SP3.
Thanks,
Kelly Greer
KellyGreer1@.nospam.com
replace nospam with yahoo
Its hardcoded. I believe after 50 words the rank drops off to 0. I also
believe that after 1366 (or some large number of words like that) you will
no longer get a hit.
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
"kellygreer1" <kellygreer1@.yahoo.com> wrote in message
news:1122912214.203288.58290@.g47g2000cwa.googlegro ups.com...
> Hello group,
> Does anyone know how near a word needs to be to another word to be
> included in the results of a CONTAINS search that uses NEAR? Is this
> setting adjustable? Is is stored in the registry? INI or config file?
> I'm using SQL Server 7 SP3.
> Thanks,
> Kelly Greer
> KellyGreer1@.nospam.com
> replace nospam with yahoo
>
|||Kelly,
Q. Does anyone know how near a word needs to be to another word to be
included in the results of a CONTAINS search that uses NEAR?
A. Within 50 non-noise words. Additionally, end-of-sentence and
end-of-paragraph also have an effect on the "nearness" of one word or phrase
to another word or phrase.
Q. Is this setting adjustable?
A. No. This is hard-coded.
Q. Is it stored in the registry? INI or config file?
A. No and No. Although, I would hope in some future SQL Server version
(post-SQL Server 2005) that this would be possible, IMHO.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"kellygreer1" <kellygreer1@.yahoo.com> wrote in message
news:1122912214.203288.58290@.g47g2000cwa.googlegro ups.com...
> Hello group,
> Does anyone know how near a word needs to be to another word to be
> included in the results of a CONTAINS search that uses NEAR? Is this
> setting adjustable? Is is stored in the registry? INI or config file?
> I'm using SQL Server 7 SP3.
> Thanks,
> Kelly Greer
> KellyGreer1@.nospam.com
> replace nospam with yahoo
>

Question about Proximity (NEARness) with Full Text Indexing on SQL Server 7

Hello group,

Does anyone know how near a word needs to be to another word to be
included in the results of a CONTAINS search that uses NEAR? Is this
setting adjustable? Is is stored in the registry? INI or config file?

I'm using SQL Server 7 SP3.

Thanks,
Kelly Greer
KellyGreer1@.nospam.com
replace nospam with yahooIts hardcoded. I believe after 50 words the rank drops off to 0. I also
believe that after 1366 (or some large number of words like that) you will
no longer get a hit.

--
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
"kellygreer1" <kellygreer1@.yahoo.com> wrote in message
news:1122912214.203288.58290@.g47g2000cwa.googlegro ups.com...
> Hello group,
> Does anyone know how near a word needs to be to another word to be
> included in the results of a CONTAINS search that uses NEAR? Is this
> setting adjustable? Is is stored in the registry? INI or config file?
> I'm using SQL Server 7 SP3.
> Thanks,
> Kelly Greer
> KellyGreer1@.nospam.com
> replace nospam with yahoo|||Kelly,
Q. Does anyone know how near a word needs to be to another word to be
included in the results of a CONTAINS search that uses NEAR?
A. Within 50 non-noise words. Additionally, end-of-sentence and
end-of-paragraph also have an effect on the "nearness" of one word or phrase
to another word or phrase.

Q. Is this setting adjustable?
A. No. This is hard-coded.

Q. Is it stored in the registry? INI or config file?
A. No and No. Although, I would hope in some future SQL Server version
(post-SQL Server 2005) that this would be possible, IMHO.

Regards,
John
--
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/

"kellygreer1" <kellygreer1@.yahoo.com> wrote in message
news:1122912214.203288.58290@.g47g2000cwa.googlegro ups.com...
> Hello group,
> Does anyone know how near a word needs to be to another word to be
> included in the results of a CONTAINS search that uses NEAR? Is this
> setting adjustable? Is is stored in the registry? INI or config file?
> I'm using SQL Server 7 SP3.
> Thanks,
> Kelly Greer
> KellyGreer1@.nospam.com
> replace nospam with yahoo

question about lowercase in sql

Hi,
the nvarchar field "myfield" contains the stringvalue 'myvalue' (in lower
case).
I did this sql statement:
select myfield from mytable where myfield='MYVALUE'
and .. i got the record.
May i conclude that SQL does make no difference between 'MYVALUE' and
'myvalue'?
Thanks
BobOn Sep 7, 1:41 pm, "Bob" <n...@.spam.ur> wrote:
> Hi,
> the nvarchar field "myfield" contains the stringvalue 'myvalue' (in lower
> case).
> I did this sql statement:
> select myfield from mytable where myfield='MYVALUE'
> and .. i got the record.
> May i conclude that SQL does make no difference between 'MYVALUE' and
> 'myvalue'?
> Thanks
> Bob
The answer is yes. SQL server is not case sensitive.|||Thanks
"SB" <othellomy@.yahoo.com> schreef in bericht
news:1189151637.431898.75760@.o80g2000hse.googlegroups.com...
> On Sep 7, 1:41 pm, "Bob" <n...@.spam.ur> wrote:
>> Hi,
>> the nvarchar field "myfield" contains the stringvalue 'myvalue' (in lower
>> case).
>> I did this sql statement:
>> select myfield from mytable where myfield='MYVALUE'
>> and .. i got the record.
>> May i conclude that SQL does make no difference between 'MYVALUE' and
>> 'myvalue'?
>> Thanks
>> Bob
> The answer is yes. SQL server is not case sensitive.
>|||This answer isn't necessarily true. The column collation is used which
determines case sensitivity. It can be overridden at the TSQL statement level
using COLLATE, but if this is not there, you have to refer to the column's
collation.
HTH,
Paul Ibison|||Hello Bob,
I just want to prevent a possible misunderstanding.
SQL Server is not always "case insensetive". This is about the collation
settings that you set when you setup SQL Server.
If you selected "Case Sensetive" when you set it up, then your current query
would return nothing.
Please read below document from BOL for more information about this setting:
http://msdn2.microsoft.com/en-us/library/ms143508.aspx
--
Ekrem Önsoy
"Bob" <no@.spam.ur> wrote in message
news:OpBGlTS8HHA.484@.TK2MSFTNGP06.phx.gbl...
> Thanks
> "SB" <othellomy@.yahoo.com> schreef in bericht
> news:1189151637.431898.75760@.o80g2000hse.googlegroups.com...
>> On Sep 7, 1:41 pm, "Bob" <n...@.spam.ur> wrote:
>> Hi,
>> the nvarchar field "myfield" contains the stringvalue 'myvalue' (in
>> lower
>> case).
>> I did this sql statement:
>> select myfield from mytable where myfield='MYVALUE'
>> and .. i got the record.
>> May i conclude that SQL does make no difference between 'MYVALUE' and
>> 'myvalue'?
>> Thanks
>> Bob
>> The answer is yes. SQL server is not case sensitive.
>|||Respectfully, this is also only partially true. The collation setting chosen
during the installation becomes the default for the new databases, but it may
be overridden during database creation (or afterwards). Likewise, the
database collation becomes the default for new text-based columns, but this
may also be overridden. The column-level collation is the one being used in
the query, provided that the keyword COLLATE isn't used.
Cheers,
Paul Ibison|||Thanks for addition ;)
--
Ekrem Ã?nsoy
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:A8FE3DCB-F05A-4A4A-B76C-D8CBE3C0C957@.microsoft.com...
> Respectfully, this is also only partially true. The collation setting
> chosen
> during the installation becomes the default for the new databases, but it
> may
> be overridden during database creation (or afterwards). Likewise, the
> database collation becomes the default for new text-based columns, but
> this
> may also be overridden. The column-level collation is the one being used
> in
> the query, provided that the keyword COLLATE isn't used.
> Cheers,
> Paul Ibison
>sql

Question about FullText Search

Hi eveyone,

I have a fullText catalog for a very simple table with 3 rows which contains text like below:

Row 1==> First term, Second term 4-3/16" third term 14.75 forth term 998 3-3/8" 8911 8
Row 2==> First term, Second term 5-3/16" third term 14.95 forth term 11
Row 3==> First term, Second terms 2/18" third term 14.07 forth term 3-3/8" 3

When I try to run query:

1. Select * from myFullText where contains(Text, '3/16') return row 1 and 2 ( ok )
2. Select * from myFullText where contains(Text, '11-3/8') ==> return row 2 (matching 11 only)
3. Select * from myFullText where contains(Text, '3-3/8') return no record
4. Select * from myFullText where contains(Text, '3/8') return no record

If someone do understand about Microsoft FullText search, please help me by explain to me why the output for sql #2, 3 and 4 are like that.

Regards,

John Dang

FYI,

Currently I am using SqlServer 2005, english language and Window XP Pro OS.

JDang

|||

Workaround:

Add more keywords:

3-3/8 + 3/8 + 3-3 + 3 + 338 ...

Consider to eliminate slashes and dashes

Make sure that noisewords do not disdurb. ( I dont know enough about when they are used )

Thomas Boffo

Question about FullText Search

Hi eveyone,

I have a fullText catalog for a very simple table with 3 rows which contains text like below:

Row 1==> First term, Second term 4-3/16" third term 14.75 forth term 998 3-3/8" 8911 8
Row 2==> First term, Second term 5-3/16" third term 14.95 forth term 11
Row 3==> First term, Second terms 2/18" third term 14.07 forth term 3-3/8" 3

When I try to run query:

1. Select * from myFullText where contains(Text, '3/16') return row 1 and 2 ( ok )
2. Select * from myFullText where contains(Text, '11-3/8') ==> return row 2 (matching 11 only)
3. Select * from myFullText where contains(Text, '3-3/8') return no record
4. Select * from myFullText where contains(Text, '3/8') return no record

If someone do understand about Microsoft FullText search, please help me by explain to me why the output for sql #2, 3 and 4 are like that.

Regards,

John Dang

FYI,

Currently I am using SqlServer 2005, english language and Window XP Pro OS.

JDang

|||

Workaround:

Add more keywords:

3-3/8 + 3/8 + 3-3 + 3 + 338 ...

Consider to eliminate slashes and dashes

Make sure that noisewords do not disdurb. ( I dont know enough about when they are used )

Thomas Boffo