Page Comparison

autoGenSQL

A TRUE or FALSE value that determines if SQL is automatically generated from Datical functions

deployThreshold

Pick one of the 3 available options:

• stopOnError - Deployment will not be performed when errors are present in Pre-Deployment validation
• stopOnWarn - Deployment will not be performed when errors and/or Warnings are present in Pre-Deployment validation
• deployAlways - Deploy will occur regardless of validation results. NOT RECOMMENDED

externalStoredLogic

A TRUE or FALSE value that determines if storedLogic is inline or in external files

invalidsCheck

Oracle, SQL Server, or DB2 only

Determines the type of validity check for compiled objects
disabled - No check

limited - Only check objects targeted by a deployment and their dependencies

local - Check objects in all schemas specified in the deployment plan
global - Check across the entire database

invalidsAction

Oracle, SQL Server, or DB2 only

Determines what to do when the Stored Logic Validity Check fails. 

Both existing objects already in the database and new objects being deployed are checked.  

• warn - print WARN message and continue
  • New objects that fail - print WARN message
  • Existing objects that fail - print WARN message
• fail - print WARN or ERROR message, depending on objects
  • New objects that fail - print ERROR message
  • Existing objects that fail that were not targeted by a changeset in the deploy operation - print WARN message
  • (7.7 & later) Existing objects that fail that were targeted by a changeset in the deploy operation - print ERROR message

requireOptions

A TRUE or FALSE value that determines if Forecast and Deploy Options are always required

deployMode

Datical DB can optionally perform a full set of rules validations and deployment simulation prior to deploying the changes to the database. This is called a "Full" deploy. If you typically do a Forecast and then a deploy, you can set the deployMode to "quick" to skip the forecast and rules validation steps that happen during a Full deploy.

Valid values for this setting are:

• quick
• full

dbSchemaDefinition

The value of this setting determines whether the schema managed by this Plan are defined once for all Deployment Steps in the Plan (value: 'project') or specified independently with each Deployment Step (value:'dbDef') .  For multi-schema projects, this value should always be 'project'.  

multiCatalog

SQL Server only

multiSchema

A TRUE or FALSE value to indicate whether this Deployment Plan manages more than one schema. 

trackingSchema

The schema that should host the Datical Tracking Tables for the Deployment Steps in this Plan.

managedSchema

A comma-separated list of the schema to be managed by the Deployment Plan. They must be valid and available for the database specified by schemaSelectionStep.

schemaSelectionStep

DbDef to use for the list of managed schema in managedSchema. 

limitForecast

A TRUE or FALSE value that optimizes the forecast by limiting the objects under consideration to the ones that are getting deployed (instead of the entire database)

enableRowCount

Pick one of the 3 available options:

• exact - Use a table scan to collect the row count. 
• approximate - Use statistics to estimate the row count.
• disabled - Do not collect row counts.

Before v5.7, the semantics were true|false.  When read in v5.7 or later, true is mapped to exact and false is mapped to disabled. 

forecastDML
Oracle only

A TRUE or FALSE value that enables DML forecasting.

enableDdlLockTimeout

Oracle only

ddlLockTimeoutValue

Oracle only

DDL commands require exclusive locks on internal structures. If these locks are not available some commands return with an "ORA-00054: resource busy" error message, which can be frustrating when trying to modify objects that are accessed frequently. To get round this Oracle 11g includes the DDL_LOCK_TIMEOUT parameter, which can be set at instance or session level using the ALTER SYSTEM and ALTER SESSION commands respectively.

The DDL_LOCK_TIMEOUT parameter indicates the number of seconds a DDL command should wait for the locks to become available before throwing the resource busy error message. The default value is zero.

runtimeCredentials

Do not use this field, it does not have any effect.
Set the DbDefClass with the prefix DelayedCredential instead

enableSqlParser

Oracle only