 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Full-Text Search / July 2007Update to SP4 causes starnge Server behavior
Hi, I updated our SQL Sever 200 to SP4 yesterday. Since that update we have the problem that some FTS queries are timing out and afterwards it it not possible to do any FTS queries and we have to reboot the server. With SP3 the same queries caused no problems. The porblems only occur if there is a 'NEAR' operatar in the query. Is ther a solution for this porblem or should we go back to SP3? But how could we got back to SP3? WE use Windows 2000 Server und the neutral langagugae breaker. thx gerald What kind of problem? SP4 suppose fix the issue listed in the article below. Ref Link: http://support.microsoft.com/kb/888008/EN-US/  SignatureMohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 > Hi, > [quoted text clipped - 10 lines] > > thx gerald Queries with NEAR operators (not all of them) cause a query timeout an afterwards i have to reboot the server, because every fts query times out. > What kind of problem? > [quoted text clipped - 16 lines] > > > > thx gerald Did you try rebuilding the index or re-doing the FTS Catalog? And next time FTS mucks up maybe try just restarting the service? Thanks! SignatureMohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 I tried all of that, but the only way to get the fts running, is to restart the server. > Did you try rebuilding the index or re-doing the FTS Catalog? And next time > FTS mucks up maybe try just restarting the service? Thanks! Have your catalogs finished building? IIRC Service Pack 4 involves a rebuilding of your full-text catalogs. From: http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-C44E06B0D2A 3/ReadmeSql2k32sp4.htm#_full-text_catalogs_will_be_rebuilt_after_setup_completes All full-text catalogs are rebuilt as part of the installation of SP4 when upgrading from SP2 or earlier. The rebuild is automatic and resource-intensive. Queries against full-text catalogs may return partial results or no results until the rebuild process is complete. After SP4 is installed, the system event logs contain messages stating that the catalogs were corrupt, of an older version, and had to be rebuilt. For information , see the Knowledge Base article 327217, which also discusses possible workarounds for keeping full-text search available during the rebuild process and to avoid an automatic rebuild. Also the algorithim changed between the two service packs. You might want to set remote timeout to a larger value to see if this helps. sp_configure 'remote query timeout (s)' ,10000 reconfigure with override SignatureLooking 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 >I tried all of that, but the only way to get the fts running, is to restart > the server. > >> Did you try rebuilding the index or re-doing the FTS Catalog? And next >> time >> FTS mucks up maybe try just restarting the service? Thanks! Thanks for your help, Hillary and Mohit. I uninstalled SQL server today and reinstalled it afterwards with SP4 and everything works fine now. thx, Josef > Have your catalogs finished building? IIRC Service Pack 4 involves a > rebuilding of your full-text catalogs. [quoted text clipped - 26 lines] > >> time > >> FTS mucks up maybe try just restarting the service? Thanks! |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.