SQL Server Equivalents
Just curious as to what you think is lacking. I'm guessing "ease of administration" tools.
"Welcome to Rivendell, Mr. Anderson..."
I assume it's issues with add-ons.
E.g. Some business requires a particular tool that is only supported when it talks to SQL Server.
Just my guess, though.
Boxed vertical market software, I wot.
They're the bits there's no replacement for.
I have a badly organised desk drawer that's more than a match for SQL Server itself.
[link|http://www.no2id.net/|Don't Let The Terrorists Win]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
Use P2P for legitimate purposes!
[link|http://kevan.org/brain.cgi?pwhysall|A better terminal emulator]
Well, sort of boxed.
Believe it or not a lot of packages, even ones with national distribution, still come as a CD tucked in the pocket of a loose leaf manual binder - just like in the old days of CP/M-80 (but it was a floppy back then).
Ease of administration is irrelevant.
So is actual functionality of the engine.
What is important is the software house will only support it on SQL Server, or on the Windows version of some other database.
Since all specialty software has flaws and quirks it's a bad business decision not to follow the vendor's recommendations to the letter. If a problem comes up they'll grasp the first straw they see and refuse support.
I know what it's lacking.
It's not a problem unique to MS SQL Server, unfortunately, as *all* the database engines have their unique variant of SQL - Oracle, Sybase, even MySQL and PostGresQL. Some have fewer extensions than others, mind you, but few OTS applications are capable of talking to 'any' SQL backend: they are almost always coded to talk to a specific one. It's a bit like the home computer BASIC wars writ large.