Skip to content

Commit 364cbae

Browse files
committed
Update TTL
1 parent 97114bd commit 364cbae

File tree

3 files changed

+4
-3
lines changed

3 files changed

+4
-3
lines changed

articles/data-factory/includes/data-factory-v2-connector-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ms.author: jianleishen
2323
| &nbsp; | [Azure Databricks Delta Lake](../connector-azure-databricks-delta-lake.md) | ✓/✓ | ✓/✓ <small>Use [delta format](../format-delta.md)</small> || | ||
2424
| &nbsp; | [Azure Files](../connector-azure-file-storage.md) | ✓/✓ | ||||✓<small> Exclude storage account V1 |
2525
| &nbsp; | [Azure SQL Database](../connector-azure-sql-database.md) | ✓/✓ | ✓/✓ <br> ||| ||
26-
| &nbsp; | [Azure SQL Managed Instance](../connector-azure-sql-managed-instance.md) | ✓/✓ | ✓/✓ <br> ||| |<small> Public preview |
26+
| &nbsp; | [Azure SQL Managed Instance](../connector-azure-sql-managed-instance.md) | ✓/✓ | ✓/✓ <br> ||| ||
2727
| &nbsp; | [Azure Synapse Analytics](../connector-azure-sql-data-warehouse.md) | ✓/✓ | ✓/✓ ||| ||
2828
| &nbsp; | [Azure Table Storage](../connector-azure-table-storage.md) | ✓/✓ | || | |✓<small> Exclude storage account V1 |
2929
| **Database** | [Amazon RDS for Oracle](../connector-amazon-rds-for-oracle.md) | ✓/− | || | ||

articles/data-factory/managed-virtual-network-private-endpoint.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,7 @@ Interactive authoring capabilities are used for functionalities like test connec
8989
### Copy activity
9090

9191
By default, every copy activity spins up a new compute based upon the configuration in copy activity. With managed virtual network enabled, cold computes start-up time takes a few minutes and data movement can't start until it's complete. If your pipelines contain multiple sequential copy activities or you have many copy activities in foreach loop and can’t run them all in parallel, you can enable a time to live (TTL) value in the Azure integration runtime configuration. Specifying a time to live value and DIU numbers required for the copy activity keeps the corresponding computes alive for a certain period of time after its execution completes. If a new copy activity starts during the TTL time, it will reuse the existing computes, and start-up time will be greatly reduced. After the second copy activity completes, the computes will again stay alive for the TTL time.
92+
You have the flexibility to select from the pre-defined compute sizes, ranging from small to medium to large. Alternatively, you also have the option to customize the compute size based on your specific requirements and real-time needs.
9293

9394
> [!NOTE]
9495
> Reconfiguring the DIU number will not affect the current copy activity execution.
@@ -104,7 +105,7 @@ The DIU you select in TTL will be used to run all copy activities, the size of t
104105

105106
### Pipeline and external activity
106107

107-
Unlike copy activity, pipeline and external activity have a default time to live (TTL) of 60 minutes. You can change the default TTL on Azure integration runtime configuration according to your actual needs, but it’s not supported to disable the TTL.
108+
Similar to the copy, you have the ability to tailor the compute size and TTL duration according to your specific requirements. However, unlike the copy, please note that pipeline and external TTL cannot be disabled.
108109

109110
> [!NOTE]
110111
> Time to live (TTL) is only applicable to managed virtual network.
@@ -120,7 +121,7 @@ The following table lists the differences between different types of TTL:
120121
| ----------------- | ---------- | -------- | --------------- |
121122
| When to take effect | Immediately after enablement | First activity execution | First activity execution |
122123
| Can be disabled | Y | Y | N |
123-
| Reserved compute is configurable | N | Y | N |
124+
| Reserved compute is configurable | N | Y | Y |
124125

125126
> [!NOTE]
126127
> You can't enable TTL in default auto-resolve Azure integration runtime. You can create a new Azure integration runtime for it.
55.9 KB
Loading

0 commit comments

Comments
 (0)