SharePoint Server 2013 and SQL Server Full-Text Search

There's long been some debate as to whether or not SharePoint requires you to install the SQL Server Full-Text Search feature on the database server. I've worked on the premise that it doesn't - SharePoint has its own search engine, etc.

However, the Access Services service application DOES require the Full-Text Search feature. If this feature is not installed, you'll get an error when you attempt to provision an Access Services service application that states "The Application Database Server does not have the Full-Text Search feature installed".

























Access Services actually places a whole bunch of extra demands on the database server in addition to the Full-Text Search requirement. For example:

  • The database server must be running at least SQL Server 2012 (SharePoint Server 2013 will run happily on SQL Server 2008 R2 SP1)
  • The SQL Server instance must support mixed mode authentication.
  • The SQL Server instance must support Named Pipes in addition to TCP/IP.
For more information, take a look at the SharePoint 2013: Access Services wiki page on TechNet. Of course, there's nothing to stop you using a separate SQL Server installation to host your Access Services databases. This probably isn't a bad idea if you're planning to use Access Services heavily.

Comments

  1. I have 2 SQL Servers 2014, one for SP Content and one for custom DBs. I have followed the instructions to configure my custom DB server to host the Access service dbs, but I'm still getting this error message. Any idea how I can troubleshoot? BTW, I enjoyed your MVA sessions.

    ReplyDelete
    Replies
    1. Hi Dean - is the SQL Full-text Filter Daemon Launcher service (MSSQLFDLauncher) running on the Access Services DB server? And is named pipes enabled? I don't actually have a test environment at the moment so unfortunately I can't try things out.

      Delete

Post a Comment

Popular posts from this blog

Server-side activities have been updated

The target principal name is incorrect. Cannot generate SSPI context.

Custom Workflow Activity for Creating a SharePoint Site