Hey all, we currently try to minimize the differences between our on premise datahub and the open source codebase for easier updates. So far we used MSSQL as backend and would like to continue to do so, as they are managed by another team. I aslo just saw that the question for a MSSQL backend came up already so i wanted to ask if the the datahub team would be interested in this? We enabled mssql via ebean, put the driver into build.gradle and created the table with the correct schema for the acpects manually. Apart from an init script for the database, would there be something else needed for a successful contribution?

Hi @happy-monitor-58564 that contribution would definitely be welcome, here is the postgres-setup image we build that contains the init script. Along with that, a guide for how to run DataHub with MSSQL backend would be needed.

Thanks for the Infos @mammoth-bear-12532, i have an init-container/init-script that is working, but i still need to write documentation. Is there a preferred place where i should out it and should i write more generally about using databases other than mysql (like the recent cassandra option)? I also created a docker-compose file wich uses a sql server container. This container only starts when provided the ACCEPT_EULA env variable. It then starts in the Developer Edition mode which is free for all but production environments. I'm not sure if i should also provide this setup, it could definatly help developers test changes to the init.sql, but on the other side I don't want anyone to get burned by the licensing.