Request for comment

Background

For as long as I can remember, Revolution has supported an sqlsrv driver which allows it to be installed natively on windows servers using a Microsoft SQL Server rather than MySQL.

In that same time span, I've probably encountered like... 4 installations actually using MODX on sqlsrv, the latest being this thread on the forum last week where a user was trying to figure out why extras wouldn't show up, which is because those extras do not support (or do not claim to support) the sqlsrv driver.

Proposal

Given...

• There does not appear to be much, if any, real world usage of the sqlsrv driver
• Anecdotally I don't believe many (if any at all) core integrators and contributors actively test changes against sqlsrv, at most blindly copying schema changes as needed assuming things work
• Unit tests for each commit and pull request (in github actions) are only executed in a MySQL setup
• For MODX to be useful on sqlsrv, common extras also need to support for sqlsrv, which requires explicitly providing those schemas and models which I've very rarely seen in the real world (although extras that don't have a custom table are easier to have compatible).

... I'd like to invite feedback on dropping sqlsrv support entirely from MODX as of a future major release.

That future major release could very well be 3.0 if there's a clear consensus ahead of beta. That would still give enough time to cleanup the core, update the documentation, etc.

My opinion

Properly supporting sqlsrv would require a much more intensive effort from the entire community (integrators, contributors, and extras developers) to consistently test and making sure MODX and extras operate as they should on sqlsrv.

I do not believe that effort is worth it given the lack of users, so we might as well just stop pretending it's equally supported as mysql and drop sqlsrv support as of 3.0.