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\u003eThe webpage provides reference documentation for the \u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e class in the Google Cloud Data Loss Prevention (DLP) v2 API, detailing its purpose, inheritance, implemented interfaces, and available properties, with links to different versions.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eDiscoveryCloudSqlGenerationCadence\u003c/code\u003e is used to configure how frequently Cloud SQL table profiles are refreshed, with new tables being scanned as fast as possible, subject to system capacity.\u003c/p\u003e\n"],["\u003cp\u003eThe class offers properties such as \u003ccode\u003eRefreshFrequency\u003c/code\u003e to control the frequency of data profile updates and \u003ccode\u003eSchemaModifiedCadence\u003c/code\u003e to determine when to reprofile data based on schema changes, with the default for the former being set to never.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation covers versions 4.0.0, all the way up to 4.16.0, with version 4.16.0 being the latest, down to 2.15.0.\u003c/p\u003e\n"]]],[],null,[]]
