Skip to content

Commit d77c503

Browse files
authored
Update concept-best-practices-scanning.md
1 parent 658a57c commit d77c503

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/purview/concept-best-practices-scanning.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: athenadsouza
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: conceptual
9-
ms.date: 09/14/2022
9+
ms.date: 02/23/2023
1010
ms.custom: ignite-fall-2021
1111
---
1212

@@ -143,6 +143,7 @@ After you register your source in the relevant [collection](./how-to-create-and-
143143
- **Scan type and schedule**
144144
- The scan process can be configured to run full or incremental scans.
145145
- Run the scans during non-business or off-peak hours to avoid any processing overload on the source.
146+
- **start recurrence at** must be at least 1 minute lesser than the **schedule scan time**, otherwise, the scan will be triggered in next recurrence.
146147
- Initial scan is a full scan, and every subsequent scan is incremental. Subsequent scans can be scheduled as periodic incremental scans.
147148
- The frequency of scans should align with the change management schedule of the data source or business requirements. For example:
148149
- If the source structure could potentially change weekly, the scan frequency should be in sync. Changes include new assets or fields within an asset that are added, modified, or deleted.

0 commit comments

Comments
 (0)