Describes the prerequisites for statistical semantic search and how to install or check them.
Install Semantic Search
Query the IsFullTextInstalled property of the SERVERPROPERTY (Transact-SQL) metadata function.
A return value of 1 indicates that Full-Text Search and Semantic Search are installed; a return value of 0 indicates that they are not installed.
SELECT SERVERPROPERTY('IsFullTextInstalled'); GO
To install Semantic Search, select Full-Text and Semantic Extractions for Search on the Features to Install page during SQL Server setup.
Statistical Semantic Search depends on Full-Text Search. These two optional features of SQL Server are installed together.
Install the Semantic Language Statistics Database
Semantic Search has an additional external dependency that is called the semantic language statistics database. This database contains the statistical language models required by semantic search. A single semantic language statistics database contains the language models for all the languages that are supported for semantic indexing.
Query the catalog view sys.fulltext_semantic_language_statistics_database (Transact-SQL).
If the semantic language statistics database is installed and registered for the instance, then the query results contain a single row of information about the database.
SELECT * FROM sys.fulltext_semantic_language_statistics_database; GO
The semantic language statistics database is not installed by the SQL Server setup program. To set up the Semantic Language Statistics database as a prerequisite for semantic indexing, do the following things:
1. Install the semantic language statistics database.
Locate the semantic language statistics database on the SQL Server installation media or download it from the Web.
Locate the Windows installer package named SemanticLanguageDatabase.msi on the SQL Server installation media.
Download the installer package from the Microsoft® SQL Server® 2016 Semantic Language Statistics page on the Microsoft Download Center.
Run the SemanticLanguageDatabase.msi Windows installer package to extract the database and log file.
You can optionally change the destination directory. By default, the installer extracts the files to a folder named Microsoft Semantic Language Database in the Program Files folder. The MSI file contains a compressed database file and log file.
Move the extracted database file and log file to a suitable location in the file system.
If you leave the files in their default location, it will not be possible to extract another copy of the database for another instance of SQL Server.
When the semantic language statistics database is extracted, restricted permissions are assigned to the database file and log file in the default location in the file system. As a result, you may not have permission to attach the database if you leave it in the default location. If an error is raised when you try to attach the database, move the files, or check and fix file system permissions as appropriate.
2. Attach the semantic language statistics database.
Attach the database to the instance of SQL Server by using Management Studio or by calling CREATE DATABASE (SQL Server Transact-SQL) with the FOR ATTACH syntax. For more information, see Database Detach and Attach (SQL Server).
By default, the name of the database is semanticsdb. You can optionally give the database a different name when you attach it. You have to provide this name when you register the database in the subsequent step.
CREATE DATABASE semanticsdb ON ( FILENAME = 'C:\Microsoft Semantic Language Database\semanticsdb.mdf' ) LOG ON ( FILENAME = 'C:\Microsoft Semantic Language Database\semanticsdb_log.ldf' ) FOR ATTACH; GO
This code sample assumes that you have moved the database from its default location to a new location.
3. Register the semantic language statistics database.
Call the stored procedure sp_fulltext_semantic_register_language_statistics_db (Transact-SQL) and provide the name that you gave to the database when you attached it.
EXEC sp_fulltext_semantic_register_language_statistics_db @dbname = N'semanticsdb'; GO
You can only attach and register one semantic language statistics database on an instance of SQL Server.
Each instance of SQL Server on a single computer requires a separate physical copy of the semantic language statistics database. Attach one copy to each instance.
You cannot detach a valid and registered semantic language statistics database and replace it with an arbitrary database that has the same name. Doing so will cause active or future index populations to fail.
The semantic language statistics database is read-only. You cannot customize this database. If you alter the content of the database in any way, the results for future semantic indexing are indeterministic. To restore the original state of this data, you can drop the altered database, and download and attach a new and unaltered copy of the database.
It is possible to detach or drop the semantic language statistics database. If there are any active indexing operations that have read locks on the database, then the detach or drop operation will fail or time out. This is consistent with existing behavior. After the database is removed, semantic indexing operations will fail.
Unregister, detach, and remove the Semantic Language Statistics Database
1. Unregister the semantic language statistics database.
Call the stored procedure sp_fulltext_semantic_unregister_language_statistics_db (Transact-SQL). You do not have to provide the name of the database since an instance can have only one semantic language statistics database.
EXEC sp_fulltext_semantic_unregister_language_statistics_db; GO
2. Detach the semantic language statistics database.
Call the stored procedure sp_detach_db (Transact-SQL) and provide the name of the database.
USE master; GO EXEC sp_detach_db @dbname = N'semanticsdb'; GO
3. Remove the semantic language statistics database.
After unregistering and detaching the database, you can simply delete the database file. There is no uninstall program and there is no entry in Programs and Features in the Control Panel.
Install optional support for newer document types
SQL Server installs the latest Microsoft word breakers and stemmers, but does not install the latest filters for Microsoft Office documents and other Microsoft document types. These filters are required for indexing documents created with recent versions of Microsoft Office and other Microsoft applications. To download the latest filters, see Microsoft Office 2010 Filter Packs. (There does not appear to be a Filter Pack release for Office 2013 or Office 2016.)