Versions Compared

Old Version 59

changes.mady.by.user Former user

Saved on

compared with

New Version 60

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • When configuring the repository for your SQL scripts, you may now specify which schema a script applies to in a multi-schema project. This will allow the Deployment Packager to limit it's change detection & recovery capabilities to only those schema that are impacted by the scripts being processed during that packager run. 
  • For example: If there are 30 schema in your project, but there are only scripts for 4 of the schema in this packaging run, then packager will be limited to the 4 relevant schema for that packaging run (instead of all 30 schema).  This can shorten the packager run time.  This only works if all of the scripts for that packaging run have the schemaName property set in the metadata.properties files in their folders.
  • To configure, set the value of a 'schemaName' property in the metadata.properties file for a specific directory. The value can be one schema name or a comma separated list of schema names. Do not put quotes around the schema values .  Use the casing that matches how the with Datical versions 6.12 or lower.  It is important to use casing for the value of the schemaName property that matches the casing of how your schema is listed in your datical.project file.  For example: schemaName=SCHEMA1.  Please see this page → Using the metadata.properties file
  • Setting this property does not affect script execution in any way.  It is used internally by the Deployment Packager to limit the scope of operations by schema.
  • We recommend using either schemaName property OR backup on demand:
    • If you are using backup mode "always", then the schemaName property will limit the schema list to the relevant schemas for three aspects of packager: backup, restore, and snapshot. 
    • However, if you are using backup mode "on demand" then the schemaName property will limit the schema list to the relevant schemas for only one aspect of packager: snapshot.   When you set backup to "on_demand" all of the schemas in the project will be backed up and restored, the schemas for backup/restore will NOT be limited based on the schemaName property.

...