Object locking in Flyway Desktop

• 
  Hello JR_AUS, thanks for the question.
  
  Probably not in the near future, as you can see here, the prefered and encouraged dev configuration is dedicated so it's less of a priority than in the SQL Source Control context.
  

  Peter_Laws April 07, 2023 07:14

  - 0 +
• 

  Peter_Laws said:

  Hello JR_AUS, thanks for the question.
  
  ...the prefered and encouraged dev configuration is dedicated...
  

  Thanks Peter, understood. The reality, of course, is that, for various reasons, dedicated development environments aren't always possible or desirable (we know there are pros and cons to shared and dedicated). In fact, we have met some difficulties in setting up Flyway in our enterprise environment because it has a bent toward dedicated developer databases.
  
  Our team is following the current recommended advice for a shared environment from the link you provided, which is:
  

  Recommendations if you must use a shared development database environment
  If you are unable to provision dedicated development environments, for example using Flyway Enterprise's cloning capability, Flyway Desktop can be used with a shared development database.  
  Please note that: 

  • We recommend that you leave the Repeatable Migrations feature disabled in the project if you utilize any form of branching in your version control system

  • Each person generating migrations must have their own shadow database or shadow schema

  
  Many thanks for you response.

  JR_AUS April 07, 2023 13:45

  - 0 +
• 

  Peter_Laws said:

  Hello JR_AUS, thanks for the question.
  
  ...the prefered and encouraged dev configuration is dedicated...
  

  Thanks Peter, understood. The reality, of course, is that, for various reasons, dedicated development environments aren't always possible or desirable (we know there are pros and cons to shared and dedicated). In fact, we have met some difficulties in setting up Flyway in our enterprise environment because it has a bent toward dedicated developer databases.
  
  Our team is following the current recommended advice for a shared environment from the link you provided, which is:
  

  Recommendations if you must use a shared development database environment
  If you are unable to provision dedicated development environments, for example using Flyway Enterprise's cloning capability, Flyway Desktop can be used with a shared development database.  
  Please note that: 

  • We recommend that you leave the Repeatable Migrations feature disabled in the project if you utilize any form of branching in your version control system

  • Each person generating migrations must have their own shadow database or shadow schema

  
  Many thanks for you response.

  JR_AUS April 07, 2023 13:45

  - 0 +
• 
  You can continue to use SQL Source Control for Object Locking while tracking your database changes and generating migrations for deployment with Flyway.  If you'd like to see this directly in Flyway, please add a suggestion to our UserVoice site - https://redgate.uservoice.com/forums/949477-flyway.

  StephanieHerr September 14, 2023 16:33

  - 0 +
• 

  StephanieHerr said:

  You can continue to use SQL Source Control for Object Locking while tracking your database changes and generating migrations for deployment with Flyway.  If you'd like to see this directly in Flyway, please add a suggestion to our UserVoice site - https://redgate.uservoice.com/forums/949477-flyway.

  Thank you, Stephanie.
  
  We have decided to use SQL Source Control exclusively, as Flyway does not handle our many cross-database dependencies very well.

  JR_AUS September 14, 2023 23:29

  - 0 +

Add comment

Please sign in to leave a comment.