Re:SQL Reserved Words – The Empirical List
by chasil on Wednesday October 11, 2023 @04:56PM
(#37850147)
Would not some variants of Sybase be better, as the architecture is the same, and it has supported far more platforms which allow it to scale in ways that Microsoft SQL Server cannot?
[ Parent
| on HN ]
Re:SQL Reserved Words – The Empirical List
by baq on Wednesday October 11, 2023 @05:06PM
(#37850252)
I’d been running couple TB mixed olap + oltp on 2016 a few years ago and a single cluster handled what otherwise today would be 3 or 4 different data stores today. Performance of properly tuned column stores was literally mind blowing. Haven’t even needed memory optimized tables.
Can’t comment on Sybase. Didn’t need any other platforms.
Re:SQL Reserved Words – The Empirical List
by chasil on Wednesday October 11, 2023 @06:01PM
(#37850836)
Sybase and SQL Server came from the same code until release 4.8, so it would be familiar to you.
Re:SQL Reserved Words – The Empirical List
by jeroen on Wednesday October 11, 2023 @06:39PM
(#37851278)
That was 30 years ago, though. Things have probably diverged quite a bit.
Re:SQL Reserved Words – The Empirical List
by dspillett on Thursday October 12, 2023 @05:26AM
(#37855056)
There were significant under-the-hood rewrites for SQL Server 2005 at least, and no doubt many smaller changes throughout the versions even where not adding new features, though there is still plenty that remains the same or at least very similar. I can name one bug from way-back-then which will never be fixed because maybe something somewhere “relies” on the odd behaviour!