Joshua

My feedback

  1. 78 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua supported this idea  · 
  2. 196 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua commented  · 

    I have also run across a need for having production/staging for databases in Azure. Our scenario is using release pipeline and builds created in VSTS with staging environments and slot switching of a Azure Web App.

    Using Azure CLI task it is very easy to create the staging databases either empty, copy from live DB or from backup. Using Cake or Powershell we can also manipulate the staging database if there is something that needs to be reconfigured for staging.

    So for us most of our requirements just worked in the VSTS release pipeline straight away. The only issue we ran into was https://feedback.azure.com/forums/217321-sql-database/suggestions/17367109-allow-database-to-reside-in-different-resource-gro

    For production we want to have a delete lock at the resource group level for everything but that doesn't work since the sql server and the databases need to reside in the same resource-group we cannot use azure locks on only some databases in a server to protect them from being deleted. And if we put the db server in the production group which is locked then we cannot scrap entire staging or test environments easily.

  3. 329 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    unplanned  ·  11 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Joshua supported this idea  · 

Feedback and Knowledge Base