|
|
You're in the
sql server full text search
group:Punctuation
sql server full text search:
contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of song artists/groups). Does this mean that I cannot use full-text searching at all for searching for these artist names??? Is there a work-breaker that will allow the punctuation marks (fullstops in particular), or is this a search issue rather than a word-breaker issue (i.e. CONTAINS clause does not allow punctuation anyway)?
Wozza,
Can you post the full output of -- SELECT @@version -- where you have this problem? Have you removed all single letter from the language-specific noise word files (under \FTDATA\SQLServer\Config where you have SQL Server installed) and ran a Full Population after these modifications? If not, then please do this. The default wordbreaker behavior for punctuation is dependent upon the OS-supplied wordbreaker and the @@version info will provide that. Thanks, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Wozza" <Wozza@discussions.microsoft.com> wrote in message news:4FCD6297-AF76-4DE0-A43F-9FE2B667BAB2@microsoft.com... >I am trying to improve searching performance ... but I am storing data that > contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of > song > artists/groups). > Does this mean that I cannot use full-text searching at all for searching > for these artist names??? > Is there a work-breaker that will allow the punctuation marks (fullstops > in > particular), or is this a search issue rather than a word-breaker issue > (i.e. > CONTAINS clause does not allow punctuation anyway)? >
Hi John,
select @@version produces ... Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1) [quoted text, click to view] "John Kane" wrote:
> Wozza, > Can you post the full output of -- SELECT @@version -- where you have this > problem? > Have you removed all single letter from the language-specific noise word > files (under \FTDATA\SQLServer\Config where you have SQL Server installed) > and ran a Full Population after these modifications? If not, then please do > this. The default wordbreaker behavior for punctuation is dependent upon the > OS-supplied wordbreaker and the @@version info will provide that. > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > "Wozza" <Wozza@discussions.microsoft.com> wrote in message > news:4FCD6297-AF76-4DE0-A43F-9FE2B667BAB2@microsoft.com... > >I am trying to improve searching performance ... but I am storing data that > > contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of > > song > > artists/groups). > > Does this mean that I cannot use full-text searching at all for searching > > for these artist names??? > > Is there a work-breaker that will allow the punctuation marks (fullstops > > in > > particular), or is this a search issue rather than a word-breaker issue > > (i.e. > > CONTAINS clause does not allow punctuation anyway)? > > > >
John,
I have also cleared the Noise.dat file (my index set up to use the Neutral language). If I have done this ... how do I serach for "r.e.m." for instance. Warren [quoted text, click to view] "John Kane" wrote:
> Wozza, > Can you post the full output of -- SELECT @@version -- where you have this > problem? > Have you removed all single letter from the language-specific noise word > files (under \FTDATA\SQLServer\Config where you have SQL Server installed) > and ran a Full Population after these modifications? If not, then please do > this. The default wordbreaker behavior for punctuation is dependent upon the > OS-supplied wordbreaker and the @@version info will provide that. > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > "Wozza" <Wozza@discussions.microsoft.com> wrote in message > news:4FCD6297-AF76-4DE0-A43F-9FE2B667BAB2@microsoft.com... > >I am trying to improve searching performance ... but I am storing data that > > contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of > > song > > artists/groups). > > Does this mean that I cannot use full-text searching at all for searching > > for these artist names??? > > Is there a work-breaker that will allow the punctuation marks (fullstops > > in > > particular), or is this a search issue rather than a word-breaker issue > > (i.e. > > CONTAINS clause does not allow punctuation anyway)? > > > >
Wozza,
Ok, as you're using Win2003 (Windows NT 5.2) and therefore using the langwrbk.dll wordbreaker (vs. Win2K's infosoft.dll), you can search for the three single letters using CONTAINS, for example: Note, the use of double quotes to contain all single letters: SELECT * FROM MyTable where CONTAINS(*,'"R.E.M"') If you continue to get an error, then add back a single space character in the noise.dat file under \FTDATA where SQL Server 2000 is installed and run a Full Population, then re-run the above query. Thanks, John -- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ [quoted text, click to view] "Wozza" <Wozza@discussions.microsoft.com> wrote in message news:28143E7D-BA1E-47EE-9C86-CB95D4A428ED@microsoft.com... > John, > > I have also cleared the Noise.dat file (my index set up to use the Neutral > language). > > If I have done this ... how do I serach for "r.e.m." for instance. > > Warren > > "John Kane" wrote: > >> Wozza, >> Can you post the full output of -- SELECT @@version -- where you have >> this >> problem? >> Have you removed all single letter from the language-specific noise word >> files (under \FTDATA\SQLServer\Config where you have SQL Server >> installed) >> and ran a Full Population after these modifications? If not, then please >> do >> this. The default wordbreaker behavior for punctuation is dependent upon >> the >> OS-supplied wordbreaker and the @@version info will provide that. >> >> Thanks, >> John >> -- >> SQL Full Text Search Blog >> http://spaces.msn.com/members/jtkane/ >> >> >> "Wozza" <Wozza@discussions.microsoft.com> wrote in message >> news:4FCD6297-AF76-4DE0-A43F-9FE2B667BAB2@microsoft.com... >> >I am trying to improve searching performance ... but I am storing data >> >that >> > contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of >> > song >> > artists/groups). >> > Does this mean that I cannot use full-text searching at all for >> > searching >> > for these artist names??? >> > Is there a work-breaker that will allow the punctuation marks >> > (fullstops >> > in >> > particular), or is this a search issue rather than a word-breaker issue >> > (i.e. >> > CONTAINS clause does not allow punctuation anyway)? >> > >> >> >>
ok, I tried SELECT * FROM Track where CONTAINS(*,'"R.E.M."') and SELECT * FROM Track where CONTAINS(*,'"R.E.M"') and got the same error each time ... Server: Msg 7619, Level 16, State 1, Line 1 Execution of a full-text operation failed. A clause of the query contained only ignored words. .... so I added a space to Noise.dat and am repopulating. [quoted text, click to view] "John Kane" wrote:
> Wozza, > Ok, as you're using Win2003 (Windows NT 5.2) and therefore using the > langwrbk.dll wordbreaker (vs. Win2K's infosoft.dll), you can search for the > three single letters using CONTAINS, for example: Note, the use of double > quotes to contain all single letters: > > SELECT * FROM MyTable where CONTAINS(*,'"R.E.M"') > > If you continue to get an error, then add back a single space character in > the noise.dat file under \FTDATA where SQL Server 2000 is installed and run > a Full Population, then re-run the above query. > > Thanks, > John > -- > SQL Full Text Search Blog > http://spaces.msn.com/members/jtkane/ > > > "Wozza" <Wozza@discussions.microsoft.com> wrote in message > news:28143E7D-BA1E-47EE-9C86-CB95D4A428ED@microsoft.com... > > John, > > > > I have also cleared the Noise.dat file (my index set up to use the Neutral > > language). > > > > If I have done this ... how do I serach for "r.e.m." for instance. > > > > Warren > > > > "John Kane" wrote: > > > >> Wozza, > >> Can you post the full output of -- SELECT @@version -- where you have > >> this > >> problem? > >> Have you removed all single letter from the language-specific noise word > >> files (under \FTDATA\SQLServer\Config where you have SQL Server > >> installed) > >> and ran a Full Population after these modifications? If not, then please > >> do > >> this. The default wordbreaker behavior for punctuation is dependent upon > >> the > >> OS-supplied wordbreaker and the @@version info will provide that. > >> > >> Thanks, > >> John > >> -- > >> SQL Full Text Search Blog > >> http://spaces.msn.com/members/jtkane/ > >> > >> > >> "Wozza" <Wozza@discussions.microsoft.com> wrote in message > >> news:4FCD6297-AF76-4DE0-A43F-9FE2B667BAB2@microsoft.com... > >> >I am trying to improve searching performance ... but I am storing data > >> >that > >> > contains punctuation marks ... such as "E.L.O." and "R.E.M." (names of > >> > song > >> > artists/groups). > >> > Does this mean that I cannot use full-text searching at all for > >> > searching > >> > for these artist names??? > >> > Is there a work-breaker that will allow the punctuation marks > >> > (fullstops > >> > in > >> > particular), or is this a search issue rather than a word-breaker issue > >> > (i.e. > >> > CONTAINS clause does not allow punctuation anyway)? > >> > > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |