Skip to content

Commit f020ccd

Browse files
mjosephymshsagir
andauthored
Update data-explorer/kusto/management/alter-database-streaming-ingestion-policy-command.md
Co-authored-by: Shlomo Sagir <[email protected]>
1 parent fea4e99 commit f020ccd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

data-explorer/kusto/management/alter-database-streaming-ingestion-policy-command.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Changes the database streaming ingestion policy. The [streaming policy](../manag
1414

1515
Streaming ingestion is best suited for low latency scenarios where the ingestion time is under 10 seconds for varying data volume. It can optimize processing for multiple tables across one or more databases, especially when the tables receive only a few records per second but the ingestion volume is thousands of records per second.
1616

17-
However, when the amount of data grows beyond 4 GB per hour per table, the recommendation is to switch to classic bulk ingestion instead of streaming ingestion.
17+
However, when the amount of data grows beyond 4 GB per hour per table, we recommend switching to classic bulk ingestion instead of streaming ingestion.
1818

1919
To learn how to implement streaming ingestion, see [streaming ingestion](/azure/data-explorer/ingest-data-streaming).
2020
Streaming ingestion must be enabled at the cluster level before it can be used at the database level.

0 commit comments

Comments
 (0)