I don’t think there is any possibility left to keep MS SQL Server as DB backend for Airflow.
I add Elad's message from the original discussion: https://lists.apache.org/thread/r06j306hldg03g2my1pd4nyjxg78b3h4 Because it cleary describe what is happen with MS SQL as DB backend for the last 1.5 years > During this time we hoped it would become stable and widely adopted. > To my taste MsSQL a backend has left a niche and is *not* worth the > > maintenance of it in our CI. I also want to note the following points - MS SQL have unstable tests in Airflow CI, and some cases we even don't run them for the last couple months (or even longer) - In additional it taking 2x memory than any other backend - Lack of ARM support, this is also quite important because it prevent maintainers to check some sort of things in their M1/M2 laptops - Additional backend required extra effort for any contributors who want to add new feature that touches DB This has always been an experimental feature which are described in AIrflow Release Process: https://airflow.apache.org/docs/apache-airflow/stable/release-process.html#experimental-features , I would recommend your team focuses on Airflow on Postgres rather than hanging on to vague hope that MS SQL keeping in Airflow. Quite a few companies provide Managed Airflow, see: https://airflow.apache.org/ecosystem/#airflow-as-a-service (this is not complete list) and AFAIK none of them use any other backend rather than Postgres, maybe one exception with Google Composer v1 which seems use MySQL, even on Azure Data Factory Managed Airflow use Postgres as DB backend, see: https://learn.microsoft.com/en-us/azure/data-factory/concept-managed-airflow#architecture ---- Best Wishes *Andrey Anshin* On Mon, 23 Oct 2023 at 23:01, agateaaa <agate...@gmail.com> wrote: > Hi All: > > Mssql support was voted to be dropped. > https://lists.apache.org/thread/r06j306hldg03g2my1pd4nyjxg78b3h4 > > One of our product requirements is that we can only use the Mssql database. > The product that uses airflow is installed with a suite of 8-10 other > products that all use Mssql database as their database. Preferably we do > not want our customers to install another database like postgres or MySQL > since it would involve extra overhead on their DBA team to maintain (with > backup/restore functions) yet another database > > This has been already discussed and voted on but is there any way we can > keep experimental support if we pitch in to fix any mssql related issues? > > List of current mssql issues are here > * > > https://github.com/apache/airflow/issues?q=is%3Aissue+label%3Abackend-mssql-experimintal+is%3Aopen > > Are there any other outstanding issues or can you please let us know a way > to identify mssql related bugs/problems that need to be addressed? > > e.g. > * https://github.com/apache/airflow/discussions/35114 > > > We are just trying to understand how much effort will be required to keep > supporting Mssql and if we can help with that in any way. > > Thanks > Ashwin >
