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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis document provides reference documentation for the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class within the Google Cloud Data Loss Prevention v2 API, detailing its purpose in defining how often table profiles are refreshed.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of the documentation is for version 4.16.0, and there are 23 different documented versions of the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class ranging down to version 2.15.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e implements multiple interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and is inherited from the base \u003ccode\u003eobject\u003c/code\u003e class.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class offers two properties: \u003ccode\u003eRefreshFrequency\u003c/code\u003e, which determines how often data profiles are refreshed regardless of table changes, and \u003ccode\u003eSchemaModifiedCadence\u003c/code\u003e, which determines when reprofiling occurs due to schema changes.\u003c/p\u003e\n"],["\u003cp\u003eNew tables are scanned as quickly as system capacity permits, while existing tables are refreshed according to the settings provided through the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e configuration.\u003c/p\u003e\n"]]],[],null,[]]