Synapse overwrite live mode fails

Johan á Rogvi-Hansen 106 Reputation points
2022-10-10T11:32:03.297+00:00

Hi,

When I to overwrite Synapse live mode, I can an error saying that a database already exists. How am I to circumvent this if I have other artifacts I want to publish to live mode?

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,378 questions
0 comments No comments
{count} votes

Accepted answer
  1. Bhargava-MSFT 31,261 Reputation points Microsoft Employee Moderator
    2022-10-10T21:48:33.377+00:00

    Hello @Johan á Rogvi-Hansen ,

    Welcome to the MS Q&A platform.

    As per the error message, it seems like the Database has already been published to live mode, and when you try to overwrite the live mode, it throws the error message.

    To resolve the issue:

    Method 1)

    Disconnect the Git repository (Connect to the live mode), and delete the existing Database. Once you connect back to Git, you can overwrite the live mode with your publish branch.
    Note: when you connect to the Git repository, you can't publish the changes directly from the live mode.

    Method 2) (if this is your test DB that can be deleted)
    From the collaboration branch(main) delete the DB and then commit(committed changes will reflect on the main branch) and publish(published to workspace_publish branch, which is live mode)

    Then you can able to overwrite the live mode(Here, the DB will be deleted)

    But if your requirement is to publish the artifacts to the live mode, you do not need to overwrite the live mode every time.

    Once you add any artifacts in your Collaboration branch, click on "Publish", all changes will be published to the Live mode.

    I hope this helps. Please let me know if you have any further questions.

    ------------------------------

    • Please don't forget to click on 130616-image.png and upvote 130671-image.png button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
    • Want a reminder to come back and check responses? Here is how to subscribe to a notification
    • If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators

1 additional answer

Sort by: Most helpful
  1. Steve Toutant 31 Reputation points
    2022-10-19T12:18:51.513+00:00

    While I agree with everything in this thread, there is a very important detail that should be known and it is this Best Practice (aka Limitation)

    Edit artifacts in Studio. Synapse studio is the only place you can enable workspace source control and sync changes to git automatically. Any change via SDK, PowerShell, will not be synced to git. We recommend you always edit artifact in Studio when git is enabled.
    https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/source-control#best-practices-for-git-integration

    We are having 1000 pipelines activities, we won't be doing that manually in Synapse Studio
    So, if you are using Synapse Studio to create/Modify all the artifacts it is fine. But, If you are using per example a DataWarehouse Automation tool to generate all the ETL pipelines, Linked Services, Triggers, ..., and use GIT to push to the Collaboration Branch, everything will be good in your branch, but when you'll push the PUBLISH button it might not work as expected.
    And even if in this case, the Collaboration branch is always the truth, Overwriting the Live Mode won't work easily. I'm currently trying to overwrite for 12 hours.
    I've discussed (and still discussing) about that problem with the Support.

    So, just be aware of this : "always edit artifact in Studio when git is enabled."


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.