Hi Friends,
We hope you had
an awesome week at the PASS Data Community Summit. If you attended some of the Redgate Sessions,
you may have heard some big news in the DevOps space about Flyway Desktop and
Flyway Hub.
We wanted to share more details with you and
get your feedback. We hope you can join
our FORG Hangout on Tues Nov 16 at 11:00 am ET/ 4:00 pm UK
time to see a demo and discuss these changes in more detail.
The big news –
the next versions of SQL Source Control and SQL Change Automation are re-written
from the ground up based on our comparison and Flyway technologies.
First, if you
are using SQL Source Control or SQL Change Automation, don’t worry. We will continue to develop and support these
tools for at least 3 years after we launch sometime next year. These tools have development teams dedicated
to them. We’re actively working with
large accounts to fix any issues they may experience. We’re also exploring detecting table renames
and we will support the upcoming releases of SQL Server 2021 and Visual Studio
2022.
These SQL
Server tools are loved by many users and
we’re committed to continue supporting their needs. These tools were first released over 11 years
ago and weren’t architected for the new x-database, cloud, and Git world we’re
now in. So, the next version of these
tools is re-written from the ground up in a solution called Flyway Desktop. It’s based on the Flyway migrations
technology we acquired in 2019 since it was the most popular database migration
framework and supports over 20 different databases.
Some of the
benefits of Flyway Desktop (vNext of SQL Source Control and SQL Change
Automation):
1.
x-database
support – Flyway Desktop currently has full support
for Oracle. A public preview is
available for SQL Server. We plan to GA
SQL Server support at the end of 2021 along with support for a migrations-only experience
for the 18 other databases that Flyway supports. We are planning to add full Postgres and
MySQL support in 2022, which means Flyway Desktop will have full support for the
top 4 market leading databases (SQL Server, Oracle, Postgres, and MySQL).
2.
Git-first – In addition to committing, pushing, and
pulling changes, you can create new branches and switch branches directly in Flyway
Desktop.
3.
Easier
project setup – Only one person needs to create the project. Everyone else can open the project from
version control. There’s no need for
each developer to link each database.
4.
Cloud databases – There’s less “chatting” with the development
database since it is no longer expected to be a local database. We also support the additional authentication
methods for Azure SQL DB and Managed Instances.
5.
Performance – One of the biggest complaints we get about
SQL Source Control is its performance.
Flyway Desktop limits the chatting as described above, which improves
the performance. It’s also a standalone
tool, so it will not lock up or slow down SSMS.
We’ve also taken steps to limit the number of comparisons we run to also
improve performance.
6.
Best
of both worlds – Flyway Desktop combines the benefits of SQL Source Control’s
state-based tool and the full control you get with SQL Change Automation’s migration
scripts into one tool. We still support
state-based deployments, but the new GUI can help users start adopting
migrations for continuous deployments.
7.
x-OS – Flyway Desktop is currently
available on Windows with a Mac installer coming soon. We’ll also be
releasing its cmdline on Docker.
This is a lot of information, so I hope you
can join us next Tues Nov 16 to get a demo of Flyway
Desktop for SQL Server and discuss these changes in more detail. If this date/time doesn’t work for you, we
will record and share the session afterwards. We'd be happy to setup another time to chat.
We’ll also be following up with more details about how you can try Flyway Desktop after the hangout.
Timeline· Now – Flyway Desktop available in Redgate Deploy with SQL Server support in public preview
· Tues Nov 16 at 11:00 am ET/ 4:00 pm UK time –
Join our FORG
Hangout·
End of 2021 – GA for SQL Server
· End of Q1/Q2 – Marketing launch of Flyway, which
includes Flyway Desktop
I want
to emphasize again that SQL Source Control and SQL Change Automation will continue to
be developed and supported for at least 3 years after we start to transition
users, which we expect to happen sometime in 2022. These
products are sold with a perpetual license and have active Support &
Upgrades contracts that we will honor.
We will work to make the transition experience as seamless as possible
for most users and we think your feedback, early testing, and ideas will really
help us.
I know this is
a lot of information, so I hope you can join us for the hangout. We look forward to hearing your feedback and working
together to make this a great experience.
![[Deleted User]](https://assets.zendesk.com/hc/assets/default_avatar.png)
Hi Friends,
We hope you had an awesome week at the PASS Data Community Summit. If you attended some of the Redgate Sessions, you may have heard some big news in the DevOps space about Flyway Desktop and Flyway Hub.
We wanted to share more details with you and get your feedback. We hope you can join our FORG Hangout on Tues Nov 16 at 11:00 am ET/ 4:00 pm UK time to see a demo and discuss these changes in more detail.
The big news – the next versions of SQL Source Control and SQL Change Automation are re-written from the ground up based on our comparison and Flyway technologies.
First, if you are using SQL Source Control or SQL Change Automation, don’t worry. We will continue to develop and support these tools for at least 3 years after we launch sometime next year. These tools have development teams dedicated to them. We’re actively working with large accounts to fix any issues they may experience. We’re also exploring detecting table renames and we will support the upcoming releases of SQL Server 2021 and Visual Studio 2022.
These SQL Server tools are loved by many users and we’re committed to continue supporting their needs. These tools were first released over 11 years ago and weren’t architected for the new x-database, cloud, and Git world we’re now in. So, the next version of these tools is re-written from the ground up in a solution called Flyway Desktop. It’s based on the Flyway migrations technology we acquired in 2019 since it was the most popular database migration framework and supports over 20 different databases.
Some of the benefits of Flyway Desktop (vNext of SQL Source Control and SQL Change Automation):
1. x-database support – Flyway Desktop currently has full support for Oracle. A public preview is available for SQL Server. We plan to GA SQL Server support at the end of 2021 along with support for a migrations-only experience for the 18 other databases that Flyway supports. We are planning to add full Postgres and MySQL support in 2022, which means Flyway Desktop will have full support for the top 4 market leading databases (SQL Server, Oracle, Postgres, and MySQL).
2. Git-first – In addition to committing, pushing, and pulling changes, you can create new branches and switch branches directly in Flyway Desktop.
3. Easier project setup – Only one person needs to create the project. Everyone else can open the project from version control. There’s no need for each developer to link each database.
4. Cloud databases – There’s less “chatting” with the development database since it is no longer expected to be a local database. We also support the additional authentication methods for Azure SQL DB and Managed Instances.
5. Performance – One of the biggest complaints we get about SQL Source Control is its performance. Flyway Desktop limits the chatting as described above, which improves the performance. It’s also a standalone tool, so it will not lock up or slow down SSMS. We’ve also taken steps to limit the number of comparisons we run to also improve performance.
6. Best of both worlds – Flyway Desktop combines the benefits of SQL Source Control’s state-based tool and the full control you get with SQL Change Automation’s migration scripts into one tool. We still support state-based deployments, but the new GUI can help users start adopting migrations for continuous deployments.
7. x-OS – Flyway Desktop is currently available on Windows with a Mac installer coming soon. We’ll also be releasing its cmdline on Docker.
This is a lot of information, so I hope you can join us next Tues Nov 16 to get a demo of Flyway Desktop for SQL Server and discuss these changes in more detail. If this date/time doesn’t work for you, we will record and share the session afterwards. We'd be happy to setup another time to chat. We’ll also be following up with more details about how you can try Flyway Desktop after the hangout.
Timeline· Now – Flyway Desktop available in Redgate Deploy with SQL Server support in public preview
· Tues Nov 16 at 11:00 am ET/ 4:00 pm UK time – Join our FORG Hangout
· End of 2021 – GA for SQL Server
· End of Q1/Q2 – Marketing launch of Flyway, which includes Flyway Desktop
I want to emphasize again that SQL Source Control and SQL Change Automation will continue to be developed and supported for at least 3 years after we start to transition users, which we expect to happen sometime in 2022. These products are sold with a perpetual license and have active Support & Upgrades contracts that we will honor. We will work to make the transition experience as seamless as possible for most users and we think your feedback, early testing, and ideas will really help us.
I know this is a lot of information, so I hope you can join us for the hangout. We look forward to hearing your feedback and working together to make this a great experience.