Skip to main content

Storage Mapping Deployment Failures

Storage Mapping deployment failures happen when your Environment can't properly connect to target databases and schemas. This guide covers the most common causes and how to fix them.

Version Control Commit Issues​

Storage mapping changes must be committed before deployment. If you update Storage Mappings in the UI but don't commit, your deployment won't include those changes.

  • How to fix: Check the Git modal to make sure all changes are committed and pushed. Always commit Storage Mapping changes before deploying.

Workspace vs Environment Mapping Confusion​

Workspace Storage Mappings are for development only. Each Environment needs its own separate Storage Mappings configured for deployment.

  • How to fix: Go to the Deploy tab and configure Storage Mappings separately for each Environment. Don't rely on Workspace mappings for deployment.

Overlapping Database and Schema Mappings​

When your development Workspace and deployment Environment point to the same database or schema, you'll see conflicts and unexpected behavior.

  • How to fix: Use different databases and schemas for each Environment. For example, use DEV_DB for development, QA_DB for testing, and PROD_DB for production.

Pre-Sync Validation Errors​

Before deployment, the system validates that target databases and schemas exist and are accessible. If they don't exist or can't be accessed, deployment fails.

  • How to fix: Verify that target databases and schemas exist in your data platform with proper permissions before deploying. Create any missing objects or fix access issues first.

Missing Storage Location Definitions​

This happens when Storage Locations exist in your Workspace but aren't defined in the target Environment mappings.

  • How to fix: Make sure all Storage Locations used in your Nodes are defined in the target Environment's Storage Mappings with valid database and schema references.

Permission and Access Issues​

Service accounts may not have the required permissions on target databases or schemas.

  • How to fix: Grant proper permissions to the service account for target databases and schemas. Check role assignments and warehouse access.

Deployment Plan Generation Failures​

The deployment process validates Storage Mappings at multiple stages. A failure at any stage stops the entire deployment.

  • How to fix: Review deployment plan errors carefully. Fix any Node configuration issues, circular dependencies, or invalid references before trying again.

Best Practices​

  • Separate Environment Mappings: Each Environment (DEV, QA, PROD) should map to completely different databases and schemas to avoid conflicts.
  • Commit Storage Changes: Always commit Storage Mapping changes to version control before attempting deployment.
  • Verify Database and Schema Existence: Make sure target databases and schemas exist with proper permissions before deployment.
  • Use Consistent Storage Location Names: Storage Location names should be the same across all Environments. Only the database and schema mappings should differ.