Analyzing Search in Microsoft Team Foundation Server


Search has been part of Visual Studio Team Services (VSTS) for quite some time now. Code Search was first introduced for On-Premises in Microsoft Team Foundation Server 2017 (TFS 2017). It was followed up with the support for Work Item Search in TFS 2017 Update 2. You can check the official blog post and release notes here:

Announcing Code Search on Team Foundation Server 2017

https://www.visualstudio.com/en-us/news/releasenotes/tfs2017-update2#witsearch

Since these releases, our telemetry indicates significant adoption numbers. The product team has also been actively engaging with various customers in facilitating adoption and resolving issues. The team is committed to providing incremental value add as well as making the adoption experience as seamless as possible.

During my various engagements with customers overall emails, live chats and Skype sessions, I have observed some patterns of issues which at most times required a fixed template of resolution. While the team has published official troubleshooting guide,

https://www.visualstudio.com/en-us/docs/search/code/administration#troubleshoot-search-in-team-foundation-server

not all of them are covered over here because of the verbosity of the resolution steps.

In this series of blogs, I will attempt to outline some of these resolution templates which could be useful for the TFS Admins to self-service few of these issues.

Analyzing high CPU usage in Application Tier during Search Indexing

Fixing incorrect mapping/aliases for Search Index in Team Foundation Server

Resolving Code Search failure in TFS 2017 Update 2 due to large HTTP url

Resetting Search Index in Team Foundation Server

Monitoring Search Indexing Progress and Completion in Team Foundation Server

Comments (0)

Skip to main content