Not necessarily an enterprise feature: I always forget that MS SQL Server does not allow aliases in the SELECT list to be reused further in the SELECT list, in WHERE, GROUP BY, something that I'm almost always using with SQL Anywhere. In MS SQL, you do have to repeat the expressions or use derived tables to be able to use aliases in different query clauses.

Something like

select Col1, Col1 + Col2 as Sum, SomeFunctionUsedOn(Col3) as MyCalcValue
from MyTable
where MyCalcValue > 100
order by Sum;

I could name many more samples but one of the biggest topics is the help: In that respect SQL Anywhere seems waaaaay more informative, focussed and clear than the MS counterpart.

Easy to admin. We don't have a large IT unit. Has everything we need and more.
Proxy tables / interface to other dbs.
They used to have the best conferences ever.
This forum!
When I came to the university over 20 years ago, there was no real enterprise dbms. I made the case for SQL Anywhere, after using it at my previous employer, a gas and electric utility. (I believe it was WATCOM 4 that was packaged with Powerbuilder back then.) We jumped in and never looked back. Former MS SQL developers catch on quicky and love it.

I've been using SQL Anywhere since version 7. Our company has 100+ installs across the US (PB 2019 and SA 11 or 16). Our largest account has 100+ users and 60 sales reps that use a app with Mobilink. Anytime we can't figure out a bug, we get a copy of the customer's database and log file, fire it up on a developer's PC, using dbengXX.exe, and run through the PB debugger. Generally, it takes more time to download a copy of the DB from the customers server, than to find the bug.

Installing SA 16, setting up a server (dbsrv16.exe) with a blank database, back up events, Mobilin, etc. takes less then 15 minutes.

Using MS SQL takes 2 strokes and a heart attack to do the same things.
No contest between databases.