Barney's Blog

Blog archive

So Long Sybase

Sybase is (or was) one interesting company. Founded in 1984, two of the founders, Bob Epstein and Stu Hoffman, quickly became among the most accessible and honest business leaders. SQL Server was brand new, giving Oracle and all the other DBMS players fits.

Then Sybase crafted a deal with Microsoft and Ashton-Tate, a deal finalized behind closed doors at Esther Dyson's PC Forum (I was there, just not behind the doors).

Ashton-Tate quickly fell out as it failed to deliver a truly-SQL compatible version of dBase that would front-end SQL Server.

That left Microsoft with what was essentially a full PC server version of SQL Server. Sybase's thinking, apparently, was databases running on PC-based servers were a small slice of the market. So what's the harm giving one to Redmond?

Things turned out differently as Microsoft used Sybase's own code against it, and Sybase ultimately moved away from the pure DBMS space and deftly maneuvered into data warehousing and mobile tools. The transition went so well that SAP just ponied up nearly $6 billion to buy Sybase. Not too shabby.

Will you miss Sybase, and if so, why? Answers welcome at dbarney@redmondmag.com.

Posted by Doug Barney on 05/17/2010 at 1:17 PM


Featured

  • Microsoft Adding Google G Suite Migration in Exchange Admin Center

    Microsoft's Exchange Admin Center will be getting the ability to move Google G Suite calendar, contacts and e-mail data over to the Office 365 service "in the coming weeks."

  • Qualcomm Back in Datacenter Fray with AI Chip

    The chip maker joins a crowded field of vendors that are designing silicon for processing AI inference workloads in the datacenter.

  • Microsoft To Ship Surface Hub 2S Conference Device in June

    Microsoft on Wednesday announced a June U.S. ship date for one of its Surface Hub 2S conferencing room products, plus a couple of other product milestones.

  • Kaspersky Lab Nabs Another Windows Zero-Day

    Kaspersky Lab this week described more about a zero-day Windows vulnerability (CVE-2019-0859) that its researchers recently discovered, and how PowerShell was used by the exploit.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.