How can we help you today? How can we help you today?
JR_AUS
JR_AUS said: ...I am wondering if it is just ok to create the database project folders in that repo? Answered my own question - I just created the project in a new folder in an existing local repo and Flyway recognised it. Very simple! / comments
JR_AUS said: ...I am wondering if it is just ok to create the database project folders in that repo?Answered my own question - I just created the project in a new folder in an existing local repo ...
0 votes
Hi @Jon_Kirkwood and @PeterDanielsCRB, I thought I might chip in my thoughts, having found this conversation as a result of some months of frustration using Flyway, as a Flyway Enterprise subscriber. I'll begin by saying that I think Red Gate's direction and progress for Flyway makes sense, and I can see that it will, ultimately, be an invaluable tool for database teams. That said, over the last few months I have had very long days trying to get it to work in our environment. The specific issue I have had has been with cross-database dependencies, including circular dependencies; Flyway just doesn't handle these well when a deployment to a database we can control has a dependency in an external database that we cannot. Where the external database has an object dropped that is referenced in our baseline, even if we are no longer using that object, Flyway simply stops with an error, even though the change could otherwise be deployed successfully. The behaviour makes sense, as Flyway sees an inconsistency between the baseline and the intended deployment. However, that is small comfort when there are changes that need deploying, which will function as intended, and the tool won't allow it. I recognise that Phil Factor and other celebrated database professionals have written articles to address the issues I raise here, however these solutions don't appear to scale well (we have thousands of dependencies). Further, with a very small team, time to implement them alongside the daily need to deploy changes makes them unattractive at best. The reason I am posting this comment here is because I noticed that our Flyway Enterprise subscription currently includes SQL Change Automation, SQL Source Control and SQL Clone, for which I am now thankful! In short, the Flyway issues I have had around maintaining state in source control and being able to deploy to various environments with many external dependencies are easily managed using these older tools. SQL Clone is an amazing tool and makes trivial the task of setting up databases on developer machines. Add to that that those same databases can then be source controlled using SQL Change Automation, SQL Source Control, or a combination of each, and easily deployed with no errors. My hope is that Red Gate takes its time in changing customers over to Flyway and covers off some of the difficulties that I have mentioned, that are already addressable with existing toolsets. cc: @Peter_Laws / comments
Hi @Jon_Kirkwood and @PeterDanielsCRB,I thought I might chip in my thoughts, having found this conversation as a result of some months of frustration using Flyway, as a Flyway Enterprise subscriber...
0 votes