@Xhevahir Mehalla - Thanks for the question and using MS Q&A platform.
Regarding your question, the best approach to deploy ETL code from one Synapse workspace to another Synapse workspace in the same subscription but different resource group is to use the Synapse Workspace Deployment tool in Azure DevOps or GitHub.
Here are the high-level steps to deploy ETL code from one Synapse workspace to another Synapse workspace in the same subscription but different resource group:
- Create an Azure Resource Manager (ARM) template to create or update workspace resources (pools and workspace) in the target Synapse workspace.
- Migrate artifacts like SQL scripts and notebooks, Spark job definitions, pipelines, datasets, and other artifacts by using the Synapse Workspace Deployment tool in Azure DevOps or GitHub.
- Update the service connection and data lake storage in the target Synapse workspace.
Regarding your second scenario, to deploy the same code to another workspace in a different subscription or tenant, you can follow the same steps as above. However, you will need to create a new service connection and data lake storage in the client's environment. You can use the Azure DevOps release pipeline and GitHub Actions to automate the deployment of the Synapse workspace to the client's environment.
For more details, refer to BCDR for Azure Data Factory and Azure Synapse Analytics pipelines and Transfer an entire Azure Synapse Analytics workspace to another subscription
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.