id stringlengths 14 16 | text stringlengths 2 3.14k | source stringlengths 45 175 |
|---|---|---|
8703a78ece36-13 | You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update ... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-14 | <?xml version="1.0" encoding="utf-8"?>
<SPBackupRestoreHistory>
<SPHistoryObject>
<SPId>149fc816-8927-4a32-9437-6e05c2869ab7</SPId>
<SPRequestedBy>REDMOND\pkmacct</SPRequestedBy>
<SPBackupMethod>Full</SPBackupMethod>
<SPRestoreMethod>None</SPRestoreMethod>
<SPStartTime>01/11/2016 02:30:27</SPStartTime>
<SPFinish... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-15 | Another available method is to use the Get-SPBackupHistory cmdlet, which can also provide the same information as the spbrtoc.xml file.
The next two examples show how to perform the restore operation using the Restore-SPFarm cmdlet.
Restore-SPFarm -Directory <BackupFolder> -Item "<ServiceApplicationName>" -... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-16 | When restoring a search service application, it will be automatically paused during and after the restore. To resume the service application after the restore finishes, use the following PowerShell command.
$ssa = Get-SPEnterpriseSearchServiceApplication <SearchServiceApplicationName> $ssa.ForceResume($ssa.IsPaused()... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-17 | If crawling read-only databases in the DR farm is the preferred choice, then you must consider the fact that changes in the production farm won't be replicated to the recovery farm. As we mentioned, this includes the search service analytics updates to the index and changes to configuration items such as result sources... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-18 | [reflection.assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.search") | Out-Null
$context = New-Object Microsoft.SharePoint.Client.ClientContext("http://intranet.contoso.com")
$searchConfigurationPortability = New-Object Microsoft.SharePoint.Client.Search.Portability.searchconfigurationportability($context)
... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-19 | When crawling read-only content databases in the DR farm, the site map table in the SharePoint configuration database will not be updated to register newly created sites in the production farm. This means that those sites plus the content within them will not be indexed during full or incremental crawls. To overcome th... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
8703a78ece36-20 | If there will be a requirement to maintain as much full fidelity search as possible at the DR site if there is failover, then periodic backup and restore processes could be performed. Possible scenarios are daily or weekly backup and restore procedures that are used together with read-only database crawling to maintain... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-of-disaster-recovery-for-search |
7325a735aaae-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
You can add query transforms to a Web Part, add query rules that transform queries when certain conditions are met, and you can transform all queries directed to a result source to create a specialized search experience.
SharePoint Se... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-1 | See Query variables in SharePoint Server for an overview of all the available query variables.
When a query transform replaces the incoming query, it uses a query template . A query template is a query that includes query variables, for example "{searchTerms} contenttype:picture".
If you, for example, want to... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-2 | Transforming queries for a Web Part
You can transform queries in search Web Parts, such as the Content Search Web Part and the Search Results Web Part. Query transforms on a Web Part can be overridden by a query rule or by a query transform on the result source.
Query transforms in a Web Part are most often use... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-3 | The first step in creating a query rule is to specify the context of the rule. The minimum requirement is that you specify which result source the query must target for the query rule to be applied. To create a rule that only applies to people search, for example, you would specify that the context is the result sour... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-4 | Query more common in source
Apply the query rule if the user's query is more commonly performed against a different result source than the current one. This condition uses an analysis of queries that users entered in the various result sources.
You can create a query rule that checks if a query is more commonly per... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-5 | Description
Example
Add promoted results
Show promoted results (known as Best Bets in earlier versions of SharePoint Server) above ranked results. Promoted results are best used when an item is not indexed or if it has a poor document summary. In other cases, consider changing the ranking of the results. ... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-6 | Change ranked results by changing the query
Add a query transform that changes the original query. For example, the transform can promote or demote certain results. Changing the ranking of search results, such as boosting appropriate results by their site or URL, is a common alternative to adding promoted results... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-7 | A user query is transformed first by the Web Part, then by any query rules that apply, and finally by the result source. When you configure a transform in a result source, you know that the transform changes will not be discarded or overridden, because the result source transforms the query last. You can re-use a resul... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
7325a735aaae-8 | Appending user-access information to the query. This specifies the user who is performing the query and the permissions that the user has.
Sending the query to the search index or another search provider.
Collecting and merging search results from all search providers and sending them back to the query processi... | https://learn.microsoft.com/en-us/sharepoint/search/plan-to-transform-queries-and-order-results |
ea90ec083b7a-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
This article provides a brief overview of result sources in SharePoint Server.
Note
The modern search experience in SharePoint Server 2019 gets its results from the default result source. If you change the default result source it... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-1 | The following table shows the result sources that are used by the four search experiences that are available on a default enterprise Search Center results page. Each search experience uses a different result source.
Search experiences and corresponding result sources
This search experience
Uses this preconf... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-2 | Local Reports and Data Results
Excel, Office Data Connection (ODC), or Report Definition Language (RDL) items, or items in a report library
Local SharePoint Results
All items from the local SharePoint search index except People items
Local Video Results
Videos
Pages
Pictures
Photos and... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-3 | OpenSearch 1.0/1.1
An external search provider (such as a remote search engine or feed) that uses the OpenSearch protocol to provide search results
A result source that uses a protocol other than "Local SharePoint" must also specify a URL from which to get search results, as shown in the following table.
Re... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-4 | Specifying a result source to use for a query
A query is initially associated with a result source according to the search experience in which the user performs the query. For example, if a user clicks People below a search box (see the screenshot earlier in this article) to specify the People search experience... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-5 | Configure properties of the Search Results Web Part in SharePoint Server
You can configure the search system so that a query becomes associated with an additional or a different result source under certain conditions. One way to do this is to create a query rule that displays search results from another result so... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-6 | Narrowing search results by using a query transform
You can configure the search system so that it interprets the intent of user queries and then modifies queries accordingly to provide more targeted search results. One way to do this is to use the Query Transform section that is part of the definition of each ... | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
ea90ec083b7a-7 | Default connectors in SharePoint Server
Transforming queries in result sources
About result sources and federation | https://learn.microsoft.com/en-us/sharepoint/search/understanding-result-sources-for-search |
f802d31520ec-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
The search index is the center of search. What is in your search index determines what people will find when they look for information by entering search queries or by interacting with internet or intranet pages.
This article describe... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-1 | Managed properties can have many settings. The settings on the managed property determine how the contents can be shown in search results and how people can search for it.
You can map multiple crawled properties to a single managed property. For example, you can map both the "Writer" and "Author" crawled properties t... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-2 | See the table Managed property settings overview later in this article for more information.
The search schema
The search schema is stored in the Search Administration database. The search schema contains:
The mapping between crawled properties and managed properties. This can be a mapping from one crawle... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-3 | The search index
The search index consists of a set of files in folders on a server. The content processing component processes crawled items, uses the search schema to map crawled properties to managed properties, and translates the managed properties into a format that is written to the search index. In additio... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-4 | Full-text index
A full-text index contains all the text from the searchable managed properties that are stored in that full-text index. Each full-text index is divided into weight groups, also referred to as contexts. The different contexts relate to the relative importance of a managed property, which is one of the ... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-5 | If the property is "author", a simple query for "Smith" returns items that contain the word "Smith" and items whose author property contains "Smith".
Central Administration / Site Collection Administration / Tenant Administration
Yes
Advanced Searchable Settings
Enables viewing and changing the full-text in... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-6 | Central Administration
Yes
Refinable
Yes - active: Enables using the property as a refiner for search results in the front end. You must manually configure the refiner in the web part. Yes - latent: Enables switching refinable to active later, without having to do a full re-crawl when you switch. Both... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-7 | Enables returning results independent of letter casing and diacritics used in the query.
The query "curacao" will also match "Curaçao", "curacao" and "Curacao".
Central Administration / Site Collection Administration / Tenant Administration
Yes
Complete matching
By default, search returns partial matches ... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-8 | Language neutral tokenization (SharePoint Server 2019 only)
Select language neutral tokenization if you have multilingual content and the managed property contains tags that are based on metadata term sets or other identifiers. By default, search depends on language when it breaks queries and content into parts (to... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-9 | Finer query tokenization (SharePoint Server 2019 only)
Use this setting to help users get better search results when they search in managed properties that contain metadata with non-alphanumeric characters. This setting makes queries against the managed property slower. Users who prefer to quickly enter a query and... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
f802d31520ec-10 | Yes
Company name extraction
Enables the system to extract company name entities from the managed property when crawling new or updated items. The extracted entities can later be used to set up refiners. There is one pre-populated dictionary for company name extraction. The system saves the original managed ... | https://learn.microsoft.com/en-us/sharepoint/search/search-schema-overview |
34c123a787e8-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Before users can perform searches in SharePoint Server, you must crawl or federate the content that you want them to be able to search. When you crawl content, the Search service builds a search index that users can run queries (search ... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-1 | Keep some types of content fresher than others
You can create a large number of content sources in each Search service application, but there is overhead associated with each content source. Therefore, we recommend that you create the smallest number of content sources that satisfy your other operational requirem... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-2 | File shares
Content on file shares in your organization. Security note: When the Search service crawls a file share, if the permissions on a file on the share are different from the permissions on folders that contain the file, then the permissions on the file take precedence and are used for security trimming o... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-3 | Content sources for line-of-business data
Business data content sources require that the applications hosting the data are specified in an Application Model in a Business Data Connectivity service application. You can create one content source to crawl all applications that are registered in the Business Data Connect... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-4 | The Search service application administrator has changed a content source.
A software update or service pack was installed on servers in the farm. See the instructions for the software update or service pack for more information.
A Search service application administrator or site collection administrator added ... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-5 | Limit or increase the quantity of content that is crawled
The options available in the properties for each content source vary depending on the content source type that you select. You can use crawl setting options to limit or increase the quantity of content that is crawled. For each content source, you can spec... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-6 | You want to limit how deep to crawl the links on the start addresses.
Custom — Specify the number of pages deep and number of server hops to crawl. Note: For a highly connected site, we recommend that you start with a small number, because specifying more than three pages deep or more than three server hops ca... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-7 | Other considerations when planning content sources
For content repositories that are of the same type, such as SharePoint sites, your decision about whether to use one or more content sources depends largely upon administrative considerations. To make administration easier, organize content sources in such a way ... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-8 | Enable content on SharePoint sites to be crawled as HTTP pages. This option enables the Search system to crawl SharePoint sites that are behind a firewall or in scenarios in which the site being crawled restricts access to the Web service that is used by the crawler (a crawl component in the search topology).
Speci... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-9 | Important
Ensure that the domain account that is used for the default content access account or any other content access account is not the same domain account that is used by an application pool associated with any Web application that you crawl. Doing so can cause unpublished content in SharePoint sites and minor v... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-10 | The content processing component has a format handler that can parse the file format.
The content processing component is enabled to parse files that have the file format and file name extension.
If the content processing component is unable to parse a file, the search index will only include file properties,... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-11 | Plan to use (custom) entity extractors
You can configure the search system to look for "entities" in unstructured content, such as in the body text or the title of a document. These entities can be words or phrases, such as product names. To specify which entities to look for, you can create and deploy your own d... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-12 | Word Part Exact Extraction
Case-sensitive, maximum 1 dictionary. For example, the entry "anchor" would match "anchor" and within "anchorage", but not "Anchor".
About result sources and federation
In SharePoint Server, you use a result source to specify the URL of a provider to get search results from, a... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-13 | Divisional search variability - When an organization uses federation, each division within the organization can provide and control its own search environment. Each division can tailor search to its own requirements and preferences, with its own user experience and its own search connectors, for example. A centralized... | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
34c123a787e8-14 | Default crawled file name extensions and parsed file types in SharePoint Server
Search connector framework in SharePoint 2013 | https://learn.microsoft.com/en-us/sharepoint/search/plan-crawling-and-federation |
24a059b0dec3-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
These best practices for organizing SharePoint Server content and applying useful metadata will help make sure that the right content is included in the search index and that the right content is returned in search results.
Keep your ... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-for-organizing-content-for-search |
24a059b0dec3-1 | URLs and other metadata of files, such as file names, are analyzed linguistically by the search system. If you use natural language for URLs and for metadata, the search system can more easily understand what information is in the site or file and give it an appropriate ranking in the results. It's much easier for the ... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-for-organizing-content-for-search |
24a059b0dec3-2 | If possible, keep content in different languages on different sites. If the search system can't detect the language of a particular content item, it assumes that it is in the language of the site where it's stored.
Avoid mixing languages in content and that content's metadata. Use the same language in the metadata ... | https://learn.microsoft.com/en-us/sharepoint/search/best-practices-for-organizing-content-for-search |
156430465f95-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
This article lists the minimum hardware requirements for virtual machines and physical servers for search topologies for Internet sites.
This article also provides basic guidance on the scaling of search topologies to improve performa... | https://learn.microsoft.com/en-us/sharepoint/search/scale-search-for-internet-sites |
156430465f95-1 | Note
The medium search topology example is optimized for physical hardware, but you can deploy it on virtual machines as well.
Application servers and Web servers hosting search components
Search component on the physical server
RAM
Hard disk
Processor
Index component
48 GB for each serv... | https://learn.microsoft.com/en-us/sharepoint/search/scale-search-for-internet-sites |
156430465f95-2 | Hard disk
80 GB for system drive. Hard disk space depends on the amount of content.
Performance considerations for a medium Internet sites topology
A medium Internet sites (FIS) topology is optimized for a corpus size of 3,400,000 items, processing approximately 100-200 documents per second, dependin... | https://learn.microsoft.com/en-us/sharepoint/search/scale-search-for-internet-sites |
156430465f95-3 | Query latency
Query latency is influenced by caching, anonymous access and by other factors such as the number and complexity of query rules that are applied and triggered. Also, consider the disks on which the search index is stored; a disk that has multiple spindles can improve the access speed of the disk and redu... | https://learn.microsoft.com/en-us/sharepoint/search/scale-search-for-internet-sites |
f55b911523d1-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
If your search environment has specific performance requirements that weren't met by following the guidance in Plan enterprise search architecture in SharePoint Server 2016 , then the solution is to scale the topology of your enterpris... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-1 | Step 1: What are the specific performance requirements?
Ensure that you understand the business needs behind the specific performance requirements. For example, news and financial search require fresh data that are indexed near real-time, while litigation support services require ingestion of batches of data that... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-2 | If the analytics components don't complete their analyses quickly enough, scale up the processor resources, disk IOPS or network bandwidth of the servers hosting analytics components.
Note that we don't support unlimited scale-out of the number of search components or databases. Look up the maximum limits in Sea... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-3 | Crawl database
Use one crawl database for each 20 million items in the content corpus. For example, an index with 100 million items requires five crawl databases. If the increased amount of indexed items implies a higher crawl rate, you also need more IOPS resources to serve the crawl databases. If your crawl rate... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-4 | How to increase the ingestion rate and the freshness of results
There are some situations where you might need to increase the ingestion rate. One example is if your environment requires very fresh results and the content volume is close to the upper item limit for your search architecture, or the content changes... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-5 | Follow the guidelines to increase the ingestion speed in these time periods.
Guideline
Improve freshness for a specific content source
Increase processing resources for crawling
Increase processing resources for the crawl database
Increase processing and memory resources for cont... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-6 | Increase processing resources for the crawl database
Check whether the SQL servers hosting crawl databases have enough resources. Read how to do this in Best practices for SQL Server in a SharePoint Server farm .
If all the crawl databases use a lot of processor resources, consider adding more processor resour... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-7 | If you add more partitions on a running installation, the index repartitions itself. It can take several hours, or days, for the index to repartition. How long time it takes depends on the state of the farm when repartitioning begins.
How to reduce query latency and increase query throughput
How many queries se... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-8 | Reduce the waiting time for queries
Consider these actions:
Add more replicas of the index. When you add more replicas, search distributes queries across the replicas and works on them in parallel. An index component represents one index replica. All partitions must have the same number of replicas, so add on... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-9 | How to decrease analytics processing time
Analytics processing takes place every night. The analytics processing component stores intermediate data on the server hosting the component, and stores the results of the analysis in the analytics reporting database. If a fault hinders processing of analytics, this will... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-10 | How to make your search components and databases redundant
Your search architecture supports high availability when you host redundant search components and databases on separate fault domains. We recommend designing your search topology with redundant search databases and components. All the sample search archit... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-11 | Make crawling, content processing, query processing, analytics processing, and search administration redundant
Let's use the crawl component as an example. If you need to take down one of the servers hosting a crawl component for maintenance, this might reduce the freshness of results but search can still crawl a... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-12 | Step 4: Which server to host which search component or database?
Now that you've redesigned your search topology, your next step is to assign the search and database components to physical or virtual servers. There isn't one optimal way to assign search components to physical servers or virtual machines, but we'v... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-13 | The next step is to plan the hardware you'll need:
Choose amount of hardware resources for the host servers
General storage
Minimum resources for the index component
Minimum resources for the analytics processing component
Minimum resources for the crawl, content processing, query processing, and se... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-14 | General storage
Make sure that each host server has sufficient disk space for the base installation of the Windows Server operating system and for the SharePoint Server 2016 program files. The host server also needs free hard disk space for diagnostics such as logging, debugging, and creating memory dumps, for da... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-15 | 2 You can use 16 GB RAM and four CPU cores with SharePoint Server 2016, but then each index component can maximum hold 10 million items (instead of 20 million items).
Minimum resources for the analytics processing component
These are the minimum resources a server or virtual machine must have to host one analyt... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-16 | If the server hosts two or more of these components, increase memory to 16 GB.
The query processing component requires good network bandwidth. It's the number of index partitions and the size of queries and results that drive this need for network bandwidth. For example, 20 queries per second per query processing com... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-17 | Store the search component data on a separate storage volume or partition. For index components, this storage must also have high performance.
Note
You can set a custom location for search component data when you install SharePoint Server 2016 on a host. Any search component on the host that needs to store data, ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-18 | No
Yes
Crawl component
Stores downloaded content locally, before it sends it to a content processing component. Storage is limited by network bandwidth.
No
Yes
Search database IOPS requirements
Database name
IOPS requirements
Typical load on I/O subsystem.
Crawl database ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
f55b911523d1-19 | All of the sample search architectures host redundant search components on independent servers. In the sample search architectures, the rightmost host in each host pair is redundant. Here's the large search architecture with outlined redundant hosts: | https://learn.microsoft.com/en-us/sharepoint/search/redesign-for-specific-performance-requirements |
2cf52165c881-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Over time most search environments grow, both in amount of content and number of users. At some point the search environment outgrows the capacity and performance of your search architecture. The solution is to scale the topology of you... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-1 | Step 1: How much content do I have?
The volume of content that you have in your search index affects what resources you need to host the farm. Check how many items that are searchable in your existing search environment. You find this number on the Search administration page in the SharePoint Central Administra... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-2 | 0-80 million items
Medium search farm
0-40 million items
0-200 million items
Large search farm
0-100 million items
0-500 million items
Extra large search farm
Not supported
Although these sample search architectures use virtual machines, you can use both physical servers and virtual mach... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-3 | Large search farm
We've estimated that this search architecture can crawl 200 documents per second, and serve in the order of 10 queries per second. If you have between 80 and 200 million items in a SharePoint Server 2016 farm, the large search farm will probably be the most suitable farm for you. With a crawl ra... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-4 | General storage
Minimum hardware resources for the small search farm
Minimum hardware resources for the medium search farm
Minimum hardware resources for the large search farm
Plan storage performance
Choose type of storage
Search component IOPS requirements
Search database IOPS requirem... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-5 | Choose hardware resources for the host servers
Each search component and search database requires a minimum amount of hardware resources from the host server to perform well. But, the more hardware resources you have, the better the performance of your search architecture will be. So it's a good idea to have more... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-6 | The minimum storage that the analytics reporting database requires can vary. This is because the amount of storage depends on how users interact with SharePoint Server. When users interact frequently, there usually are more events to store. Check the amount of storage your current search architecture uses for the analy... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-7 | 3 With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.
Minimum hardware resources for the medium search farm
T... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-8 | 16 GB
1.8 GHz 4x CPU cores
1 Gbps
1 The number of CPU cores is specified here, not the number of CPU threads.
2 With SharePoint Server 2013 the minimum amount of resources needed are 500 GB storage, 16 GB RAM, and four CPU cores.
3 With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-9 | 8 GB
1.8 GHz 4x CPU cores
1 Gbps
Application servers that have crawl and search administration components
K, L
100 GB
8 GB
1.8 GHz 4x CPU cores
1 Gbps
Database server that have search databases
O, P, Q, R
500 GB
16 GB
1.8 GHz 4x CPU cores
1 Gbps
2 With SharePoint Server 2013 ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-10 | 1 Gbps
Application servers that have crawl, search administration, or content processing components
AA-AF
100 GB
8 GB
1.8 GHz 4x CPU cores
1 Gbps
Application servers that have analytics processing components
AG, AH
800 GB
8 GB
1.8 GHz 4x CPU cores
1 Gbps
Database servers that have ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-11 | Choose type of storage
For an overview of storage architectures and disk types, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2013) . The servers that host the index, analytics processing, and the search administration components, or search databases, require storage that can ... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
2cf52165c881-12 | Crawl database
Medium to high IOPS
10 IOPS per 1 document per second (DPS) crawl rate.
Link database
Medium IOPS
10 IOPS per 1 million items in the search index.
Search administration database
Low IOPS
Not applicable.
Analytics reporting database
Medium IOPS
Not applicable.
Cho... | https://learn.microsoft.com/en-us/sharepoint/search/redesign-topology-for-more-content-and-users |
458e2f37b249-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Before you set up your enterprise search architecture, there are quite a few things that require careful planning. Step by step, we'll help you to plan a small, a medium, large, or an extra large-size enterprise search architecture.
A... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-1 | When you have established a figure, multiply it by what you think the expected growth of that content will be over the next 12 months.
For example, if you're starting out with 12,000 indexed items, and you expect the volume of that content to triple over the next 12 months. You should plan for 36,000 searchable items... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-2 | Small search farm
We've estimated that this search architecture can crawl 50 documents per second, and serve in the order of 10 queries per second. If you have up to 20 million items in a SharePoint Server 2016 farm, the small search farm will probably be the most suitable farm for you. With a crawl rate of 50 do... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-3 | Extra large search farm
Microsoft tested this search architecture and measured that it can crawl 300-500 documents per second, and serve in the order of 10 queries per second. Only SharePoint Server 2016 supports this size search architecture. If you have up to 500 million items, a farm similar to the extra large... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-4 | Choose to run the servers physically or virtually
If you're using one of the architectures that we've estimated for you, then you'll be running your search architecture on virtual machines. Note also that although a virtual environment is easier to manage, its performance level can sometimes be slightly lower tha... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-5 | For example, when hosting virtual machines on Windows Server 2008 R2 Service Pack 1 (SP1), you can't use more than four CPU cores per virtual machine. With Windows Server 2012 or newer, you use eight or more CPU cores per virtual machine. Then you can scale out with more CPU cores for each virtual machine instead of sc... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-6 | Server
On host
Storage
RAM
Processor 1
Network bandwidth
Application server that has query processing and index components.
A, B
500 GB 2,3
32 GB 2,3
1.8 GHz 8x CPU cores 2,3
1 Gbps
Application server that has crawl, search administration, analytics and content processing components.... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-7 | Application server that has query processing and index components.
A, B, C, D
500 GB 2,3
32 GB 2,3
1.8 GHz 8x CPU cores 2,3
1 Gbps
Application server that has an index component.
A, B, C, D
500 GB 2,3
32 GB 2,3
1.8 GHz 8x CPU cores 2,3
1 Gbps
Application server that has analytics and con... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
458e2f37b249-8 | 3 With SharePoint Server 2016 you can also use 250 GB storage, 16 GB RAM, and four CPU cores, but then each index component can only hold 10 million items and the search farm only supports the same volume of content as a SharePoint Server 2013 search farm.
Minimum hardware resources for the large search farm
Th... | https://learn.microsoft.com/en-us/sharepoint/search/plan-enterprise-search-architecture |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.