CopyJob → Snowflake: Database name is hard‑coded in activity JSON and cannot be parameterised

Hi  MashfiqueFahim , 

Thank you for reaching out to Microsoft Fabric Community.

The behavior you are encountering is due to the current design of Microsoft Fabric, where the Snowflake database and schema are defined at the CopyJob activity level and stored as static properties within the activity definition. These values are not part of the connection object and are not exposed for parameterization or modification through Deployment Pipelines. As a result, during Dev -> SIT ->UAT promotion, only the connection is updated, while the database embedded in the CopyJob remains unchanged, leading to data being written to the original (Dev) database.

As recommonded by  tayloramy , please submit your requirement in the ideas forum, to implement it in the future releases.  

As an alternative to meet the requirements, it's recommended to use a Data Pipeline with Copy Activity instead of CopyJob, as this approach supports parameterization and dynamic content. With this setup, you can define the Snowflake database and schema as pipeline parameters and manage them for each environment through Deployment Pipeline rules, ensuring environment isolation and CI/CD compatibility. If you choose to use CopyJob, you will need to create and maintain separate CopyJobs for each environment (Dev, SIT, UAT) and manually set the correct Snowflake database in each, since the database value can't be changed dynamically after deployment.

Thanks!!