Sql-docs: Memory contention between sqlservr.exe and fdhost.exe. Is this still relevant ?

[pierrejeandev]

Per the doc, since SQL Server 2008, the Full-Text Engine is part of the sqlservr.exe process.
Are the remarks on memory contention between sqlservr.exe and fdhost.exe still relevant ?
May be you should clarify this point.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f1557aca-6d60-4fc0-0d33-81b595435d98
• Version Independent ID: 82924924-2519-7016-fb6d-3ed5734fd6eb
• Content: Improve the Performance of Full-Text Indexes - SQL Server
• Content Source: docs/relational-databases/search/improve-the-performance-of-full-text-indexes.md
• Product: sql
• Technology: search
• GitHub Login: @pmasl
• Microsoft Alias: pelopes

[rothja]

@pmasl Pedro, the full text index article talks a lot about FDHOST, and @pierrejeandev is wondering whether this is still valid (whether all of the process memory would be covered in sqlservr.exe). In reading the docs, it is not clear to me whether FDHOST is still used in recent versions of SQL Server. For example, https://docs.microsoft.com/en-us/sql/tools/configuration-manager/sql-full-text-filter-daemon-launcher-sql-server-configuration-manager?view=sql-server-ver15.

[pmasl]

It is current yes. Indeed in 2008, SQL doesn't rely solely on an external full-text engine, and has brought into the database engine the query compilation and execution components of FTS querying. But the FDHost is used for processing external full-text search filters and word breakers. You can see more about how this process is used with the SQL Server process in this page: https://docs.microsoft.com/en-us/sql/relational-databases/search/full-text-search?view=sql-server-ver15#architecture

please-close