none
FTS loading delays in SQL 2008R2

Answers

  • Hello,

    Thank you for your post.  For the most part how full-text works internally is very different between SQL Server 2005 and SQL Server 2008.  In  SQL Server 2005, the full-text engine was external to SQL Server and ran as MSFTESQL.exe and used an external filter daemon MSFTFD.exe.  In SQL Server 2008 and going forward, the full-text engine was incorporated into SQL Server and is part of SQLServr.exe and uses an external filter daemon FDHost.exe for word breaking.

    So, they are very different full-text engines.  However, the core issue in this knowledge base article has to do with the ability to verify the signature of a word breaker which is why when loading word breakers especially 3rd party word breakers, we have to access the internet to validate the signature of the word breaker.

    This check is across all versions of SQL Server and is turned on by default.  You can as the article indicates, turn off Signature_Verification or provide internet access to the server.  Both can expose security risks.

    The delay caused by having signature_verification turned on and not able to access the internet is really caused by how long it takes for the request to timeout.  There is no way to change the delay other than the two previously mentioned options.

    I hope this helps.

    Sincerely,

    Rob Beene, MSFT

    • Marked as answer by JRStern Thursday, October 31, 2013 11:56 PM
    Thursday, October 31, 2013 8:21 PM

All replies

  • Hi JRStern,
     
    Thank you for your question. 
     
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. 
     
    Thank you for your understanding and support.

    Best Regards,
    Allen Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Wednesday, October 30, 2013 7:23 AM
  • Hello,

    Thank you for your post.  For the most part how full-text works internally is very different between SQL Server 2005 and SQL Server 2008.  In  SQL Server 2005, the full-text engine was external to SQL Server and ran as MSFTESQL.exe and used an external filter daemon MSFTFD.exe.  In SQL Server 2008 and going forward, the full-text engine was incorporated into SQL Server and is part of SQLServr.exe and uses an external filter daemon FDHost.exe for word breaking.

    So, they are very different full-text engines.  However, the core issue in this knowledge base article has to do with the ability to verify the signature of a word breaker which is why when loading word breakers especially 3rd party word breakers, we have to access the internet to validate the signature of the word breaker.

    This check is across all versions of SQL Server and is turned on by default.  You can as the article indicates, turn off Signature_Verification or provide internet access to the server.  Both can expose security risks.

    The delay caused by having signature_verification turned on and not able to access the internet is really caused by how long it takes for the request to timeout.  There is no way to change the delay other than the two previously mentioned options.

    I hope this helps.

    Sincerely,

    Rob Beene, MSFT

    • Marked as answer by JRStern Thursday, October 31, 2013 11:56 PM
    Thursday, October 31, 2013 8:21 PM