disable exists-sql in DataDeploy

Does any one know how to disable the check for table existance for datadeploy?

DataDeploy DTD specifes this as 'exists-sql'. In our schema mapping file we haven't specified this, but still checks for table existance. We need to disable this and don't know how.

Thanks!

Find more posts tagged with

Comments

Adam Stoller

Does any one know how to disable the check for table existance for datadeploy?

DataDeploy DTD specifes this as 'exists-sql'. In our schema mapping file we haven't specified this, but still checks for table existance. We need to disable this and don't know how.

Thanks!

I've never used this, but doing a quick read in the OD Reference manual, it says (emphasis added):[indent]For the exists-sql element, you can specify a SQL statement to check for table or view existence for the table or view being used in the deployment. This is useful if a view is being used in the deployments, as you can query the system tables for the existence of the view. DataDeploy does not query the system tables for existence of views.[/indent]My reading of this does not support the use of this feature for disabling the checking for the existence of tables.

slk

Thanks for your reply! Do you any other features that disables the checking for table existance?

Adam Stoller

Thanks for your reply! Do you any other features that disables the checking for table existance?

No - and I cannot think why you would want it.
You're doing a deployment to a database. If the table doesn't exist, it should either be created or the deployment should fail - ergo, either way you'd want to verify that it exists - and if it does exist there shouldn't be any issues.

Not checking views is a bit more reasonable because although views are used often for queries, the data (I believe) is deployed to the tables and not to the views - so a view's existence should not be a significant factor in the deployment of the data.

slk

Thanks for your reply!