Skip to content

Commit 952bbae

Browse files
authored
Update synapse-link-for-sql-known-issues.md
to include link to update max text repl size for LOB columns
1 parent 4f9b100 commit 952bbae

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/synapse-analytics/synapse-link/synapse-link-for-sql-known-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The following sections list limitations for Azure Synapse Link for SQL.
2828
* sql_variant
2929
* timestamp
3030
* Source table row size can't exceed 7,500 bytes. For tables where variable-length columns are stored off-row, a 24-byte pointer is stored in the main record.
31-
* When source tables are being initially snapshotted, any source table data containing large object (LOB) data greater than 1 MB in size is not supported. These LOB data types include: varchar(max), nvarchar(max), varbinary(max). An error is thrown and data is not exported to Azure Synapse Analytics.
31+
* When source tables are being initially snapshotted, any source table data containing large object (LOB) data greater than 1 MB in size is not supported. These LOB data types include: varchar(max), nvarchar(max), varbinary(max). An error is thrown and data is not exported to Azure Synapse Analytics. Use the [stored procedure sp_configure](../sql/database-engine/configure-windows/configure-the-max-text-repl-size-server-configuration-option) to increase the configured maximum value for max text repl size option, which defaults to 64K. A configured value of -1 indicates no limit, other that the limit imposed by the data type.
3232
* Tables enabled for Azure Synapse Link for SQL can have a maximum of 1,020 columns (not 1,024).
3333
* While a database can have multiple links enabled, a given table can't belong to multiple links.
3434
* When a database owner doesn't have a mapped login, Azure Synapse Link for SQL runs into an error when enabling a link connection. User can set database owner to a valid user with the `ALTER AUTHORIZATION` command to fix this issue.

0 commit comments

Comments
 (0)