Comments
Sort by recent activity
Just running flyway auth or rather flyway auth -IAgreeToTheEula didn't work as they complained about me being offline. --- I was able to get it working with an offline permit as described on the Licensing page. I originally misunderstood what I needed to run and was trying to do flyway auth -offlinePermitPath=wherever , which would still say I was offline. Rather, the file just needs to be present somewhere and then you can proceed to invoke the other Flyway verbs. For example, flyway version -offlinePermitPath=wherever returns Enterprise as desired. Or if you set up the environment variable FLYWAY_OFFLINE_PERMIT_PATH as described on the offline permit path page, then you don't have to pass the argument either. --- Another, somewhat less convenient, approach I found was that running "C:\Program Files\Git\git-bash.exe" in the terminal launched by Flyway will open a new Git Bash terminal in the current working directory with the REDGATE_LICENSING_PERMIT variable still set, which sets it up with Enterprise from the get-go. / comments
Just running flyway auth or rather flyway auth -IAgreeToTheEula didn't work as they complained about me being offline.---I was able to get it working with an offline permit as described on the Lice...
I've done something like this with SQL Server. 1. Change your development database link to point to prod 2. Save any updated objects into your schema model 3. Change your development database back to dev 4. Use the Update development pane to push the changes from your schema model into the dev database Assuming test/uat also need to be updated, I would recommend generating the migration script and using that to deploy to test/uat, then doing a skipExecutingMigrations move for prod. / comments
I've done something like this with SQL Server. 1. Change your development database link to point to prod2. Save any updated objects into your schema model3. Change your development database back to...