I don't think anyone here is saying this is the right fix or accepting that this is even good code.  You and I both know this is a crap solution, but given the current situation, we're stuck between a rock and a hard place.

Current PR:
- Reverts behavior for affected databases only
- Individuals have acknowledged this as not being the right solution, but accept the code as a temporary workaround for an already planned hotfix release in order to spend additional time working at with the higher level code where the correct fix is needed

Proper PR:
- Doesn't touch current queries
- Affects database package code, specifically `JDatabaseDriverSqlsrv` and `JDatabaseQuerySqlsrv`
- Will require more thorough testing in an environment that most who work with the CMS do not have set up as there is a higher risk of breakage

I personally want to see the right solution implemented.  I also know that given the current situation, this is probably the quickest way to get the affected users back to an operational level again.