Skip to content

Commit e0c29b2

Browse files
authored
Merge pull request #54194 from HeidiSteen/heidist-master
Document limits are retired.
2 parents 1c9a8a5 + 60a6986 commit e0c29b2

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/search/search-limits-quotas-capacity.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -50,15 +50,15 @@ Maximum limits on storage, workloads, and quantities of indexes, documents, and
5050

5151
## Document limits
5252

53-
In most regions, Azure Search pricing tiers (Basic, S1, S2, S3, S3 HD) have unlimited document counts for all services created after November/December 2017. This section identifies the regions where limits apply, and how to determine whether your service is affected.
53+
As of September 2018, there are no longer any document limits for any new service created at any billable tier (Basic, S1, S2, S3, S3 HD) in any region. While most regions have had unlimited document counts since November/December 2017, there were five regions that continued to impose document limits. Depending on when and where you created a search service, you might still be subject to document limit constraints.
5454

5555
To determine whether your service has document limits, check the Usage tile in the overview page of your service. Document counts are either unlimited, or subject to a limit based on tier.
5656

5757
![Usage tile](media/search-limits-quotas-capacity/portal-usage-tile.png)
5858

59-
### Regions and services having document limits
59+
### Regions previously having document limits
6060

61-
Services having limits were either created before late 2017, or are running on data centers using lower-capacity clusters for hosting Azure Search services. Affected data centers are in the following regions:
61+
If the portal indicates a document limit, your service was either created before late 2017, or it was created on a data center using lower-capacity clusters for hosting Azure Search services:
6262

6363
+ Australia East
6464
+ East Asia

articles/search/search-sku-tier.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Portal and pricing pages put the focus on partition size and storage, but for ea
8787
**S3** and **S3 HD** are backed by identical high capacity infrastructure but each one reaches its maximum limit in different ways. **S3** targets a smaller number of very large indexes. As such, its maximum limit is resource-bound (2.4 TB for each service). **S3 HD** targets a large number of very small indexes. At 1,000 indexes, **S3 HD** reaches its limits in the form of index constraints. If you are an **S3 HD** customer who requires more than 1,000 indexes, contact Microsoft Support for information on how to proceed.
8888

8989
> [!NOTE]
90-
> Previously, document limits were a consideration but are no longer applicable for most Azure Search services provisioned after January 2018. For more information about conditions for which document limits still apply, see [Service limits: document limits](search-limits-quotas-capacity.md#document-limits).
90+
> Previously, document limits were a consideration but are no longer applicable for new services. For more information about conditions under which document limits still apply, see [Service limits: document limits](search-limits-quotas-capacity.md#document-limits).
9191
>
9292
9393
## Evaluate capacity

0 commit comments

Comments
 (0)