Data changes (non-schema changes) in Cloud SQL tables can't trigger
reprofiling. If you set this field, profiles are refreshed at this
frequency regardless of whether the underlying tables have changed.
Defaults to never.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[[["This document provides reference documentation for the `DiscoveryCloudSqlGenerationCadence` class within the Google Cloud Data Loss Prevention v2 API, detailing its purpose in defining how often table profiles are refreshed."],["The latest version of the documentation is for version 4.16.0, and there are 23 different documented versions of the `DiscoveryCloudSqlGenerationCadence` class ranging down to version 2.15.0."],["`DiscoveryCloudSqlGenerationCadence` implements multiple interfaces, including `IMessage`, `IEquatable`, `IDeepCloneable`, and `IBufferMessage`, and is inherited from the base `object` class."],["The `DiscoveryCloudSqlGenerationCadence` class offers two properties: `RefreshFrequency`, which determines how often data profiles are refreshed regardless of table changes, and `SchemaModifiedCadence`, which determines when reprofiling occurs due to schema changes."],["New tables are scanned as quickly as system capacity permits, while existing tables are refreshed according to the settings provided through the `DiscoveryCloudSqlGenerationCadence` configuration."]]],[]]
