Skip to content

Commit 9a2dc1d

Browse files
committed
Update limitations
1 parent ca8b778 commit 9a2dc1d

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/purview/register-scan-azure-sql-database.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: athenads
55
ms.author: athenadsouza
66
ms.service: purview
77
ms.topic: how-to
8-
ms.date: 10/28/2022
8+
ms.date: 12/05/2022
99
ms.custom: template-how-to
1010
---
1111
# Discover and govern Azure SQL Database in Microsoft Purview
@@ -40,11 +40,10 @@ When setting up scan, you can further scope the scan after providing the databas
4040

4141
* Microsoft Purview doesn't support over 800 columns in the Schema tab and it will show "Additional-Columns-Truncated" if there are more than 800 columns.
4242
* Column level lineage is currently not supported in the lineage tab. However, the columnMapping attribute in properties tab of Azure SQL Stored Procedure Run captures column lineage in plain text.
43-
* Stored procedures running remotely from data integration tools like Azure Data Factory is currently not supported
4443
* Data lineage extraction is currently not supported for Functions, Triggers.
4544
* Lineage extraction scan is scheduled and defaulted to run every six hours. Frequency can't be changed.
46-
* If sql views are referenced in stored procedures, they're captured as sql tables currently.
47-
* Lineage extraction is currently not supported, if Azure SQL Server is configured behind a private endpoint.
45+
* If SQL views are referenced in stored procedures, they're captured as SQL tables currently.
46+
* Lineage extraction is currently not supported if your Azure SQL Server disables public access or doesn't allow Azure services to access it.
4847

4948
## Prerequisites
5049

0 commit comments

Comments
 (0)