By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,412 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,412 IT Pros & Developers. It's quick & easy.

ignored words in full text indexing

P: n/a
Hi,

Just found out that this error can be solved

Server: Msg 7619, Level 16, State 1, Procedure usp_ft, Line 2
A clause of the query contained only ignored words.

triggered when executing

SELECT TOP 1000 * FROM ADS JOIN ADSFULL ON ads_adid = fads_adid
WHERE (ADS_ADID IN (SELECT FADS_ADID FROM ADSFULL
WHERE (CONTAINS(*, '"opel" AND "and" AND "astra"'))))

can be solved by changing the language specific file with noise words ...
but that's not really an option in our server configuration.

Now I wondered is there a way to query via TSQL a list of the noisewords ...
so I can exclude them before parsing the query??

I also dedected I can not catch the error in my stored procedure with the
instruction IF @@error ... So is it true that I can only handle this error
in my client software that calls the stored procedure??

Thanks a lot.
--
Kind regards,
Perre Van Wilrijk,
Remove capitals to get my real email address,
Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Perre Van Wilrijk" <pr****@AkoopjeskrantWAY.be> wrote in message
news:1O********************@scarlet.biz...
Hi,

Just found out that this error can be solved

Server: Msg 7619, Level 16, State 1, Procedure usp_ft, Line 2
A clause of the query contained only ignored words.

triggered when executing

SELECT TOP 1000 * FROM ADS JOIN ADSFULL ON ads_adid = fads_adid
WHERE (ADS_ADID IN (SELECT FADS_ADID FROM ADSFULL
WHERE (CONTAINS(*, '"opel" AND "and" AND "astra"'))))

can be solved by changing the language specific file with noise words ...
but that's not really an option in our server configuration.

Now I wondered is there a way to query via TSQL a list of the noisewords
...
so I can exclude them before parsing the query??

I also dedected I can not catch the error in my stored procedure with the
instruction IF @@error ... So is it true that I can only handle this
error
in my client software that calls the stored procedure??

Thanks a lot.
--
Kind regards,
Perre Van Wilrijk,
Remove capitals to get my real email address,


I don't believe there's any direct way to do that from TSQL, but since the
noise words are stored in a text file, you could load them into a table and
then join on it, use it in subqueries etc.

As for the error, error-handling in MSSQL is unfortunately rather messy (at
least before version 2005), and some errors must be handled by the client -
see here for more detailed information:

http://www.sommarskog.se/error-handling-I.html
http://www.sommarskog.se/error-handling-II.html

Simon
Jul 23 '05 #2

P: n/a
Thanks a lot Simon,
Perre

"Simon Hayes" <sq*@hayes.ch> wrote in message
news:41**********@news.bluewin.ch...

"Perre Van Wilrijk" <pr****@AkoopjeskrantWAY.be> wrote in message
news:1O********************@scarlet.biz...
Hi,

Just found out that this error can be solved

Server: Msg 7619, Level 16, State 1, Procedure usp_ft, Line 2
A clause of the query contained only ignored words.

triggered when executing

SELECT TOP 1000 * FROM ADS JOIN ADSFULL ON ads_adid = fads_adid
WHERE (ADS_ADID IN (SELECT FADS_ADID FROM ADSFULL
WHERE (CONTAINS(*, '"opel" AND "and" AND "astra"'))))

can be solved by changing the language specific file with noise words .... but that's not really an option in our server configuration.

Now I wondered is there a way to query via TSQL a list of the noisewords
...
so I can exclude them before parsing the query??

I also dedected I can not catch the error in my stored procedure with the instruction IF @@error ... So is it true that I can only handle this
error
in my client software that calls the stored procedure??

Thanks a lot.
--
Kind regards,
Perre Van Wilrijk,
Remove capitals to get my real email address,
I don't believe there's any direct way to do that from TSQL, but since the
noise words are stored in a text file, you could load them into a table

and then join on it, use it in subqueries etc.

As for the error, error-handling in MSSQL is unfortunately rather messy (at least before version 2005), and some errors must be handled by the client - see here for more detailed information:

http://www.sommarskog.se/error-handling-I.html
http://www.sommarskog.se/error-handling-II.html

Simon

Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.