Drop SQL Server Support ?

[SimonMellerin]

For now, we can't figure out how to backup and restore an SQL Server database properly (see #61).

As our nominal workflow needs the backup and restore features (see https://dbtoolsbundle.readthedocs.io/en/stable/anonymization/command.html and https://dbtoolsbundle.readthedocs.io/en/stable/anonymization/workflow.html), the SQL Server support, in its current state, seems pointless.

Also, we have often troubles using SQL Server docker images and we spend way too much time trying to fix them.

That's why I think we should drop SQL Server Support.

[pounard]

I'm quite sad, developing for it was fun. Although, I agree that until we do not solve the backup and restore problem, it's quite useless.

I'm OK with dropping CI and unmark it as being fully supported, but I'd still like to keep our local tests and existing implementation?

[SimonMellerin]

The problem I see to keep the existing implementation and local tests is that it will force us to continue to maintain the SQL Server compatibility.

Like for example, if we add a new anonymizers, should it be compatible or not with SQL Server ?

• If so, it will make each dev more complicated for not so much
• If not we will have some anonymizers compatible with SQL Server and other not, which is a bit odd