3 ms·
I worked on some systems in the 90's that used Sybase SQL Server (AKA Adaptive Server Enterprise, not the Anywhere version.) Maybe "Anywhere" is okay, but you'd
by icedchai 6y ago
I worked on some systems in the 90's that used Sybase SQL Server (AKA Adaptive Server Enterprise, not the Anywhere version.) Maybe "Anywhere" is okay, but you'd be laughed at if you suggested using Sybase SQL for a project these days. It's legacy tech.
- projektfu 6y agoSQL Anywhere is also legacy tech, but so is MySQL 5.x and lots of other established stuff. Sybase SQL Server was a real contender for a long time and IIRC shares a lineage with Microsoft SQL Server. All the major SQL vendors maintain a huge legacy of design dead ends that they have to continue supporting because applications were built when they were the next big thing. I used this software in its prime back in ‘97 and it was quite clever. It had none of the problems of its main competitor, Microsoft Jet (Access). MSDE was still a few years away. Plus, it was cross platform, so us Microsoft haters could get behind it, even if we felt forced to develop for the MS platform.
- redis_mlc 6y ago> Sybase SQL for a project these days. It's legacy tech. 1) SQL Anywhere is not "Sybase SQL." Different products, with SQL Anywhere being an embedded database that can run on a smartphone and replicate bidirectionally to other masters. Not many alternatives, even in 2020. 2) Legacy tech - when you care about your data, accept nothing less. Fun fact: the #1 most popular and regarded RDBMS for the past few years is considered to be MySQL, and it was the key technology that powered both Web 1.0 and 2.0. If that's legacy, I want more legacy. Source: DBA.
- icedchai 6y agoYes, I know they are different products. Early on, MySQL was known for anything but caring about your data. I've been using it since the 90's. Without "strict" mode, fields would be truncated and data types would be silently converted. Never mind the <5.x days where MyISAM was the default table type.