Genealogy of Relational Database Management Systems [pdf]
1–10 of 25 posts
Re: Genealogy of Relational Database Management Systems [pdf]
#2This is incredible to see all in one place. I’m preaching SQL to my Org. and it’s only getting preachier over the years, as I see new technologies come and go (OLAP, NoSQL and it’s many variations including Hadoop, Azure Cosmos DB).
For an Org. of our size, I’m not sure if these new fads make it any easier. Even if they helped with data streaming, we still are having to move it to a SQL warehouse where we can combine it with other Org. data to answer business questions. Not sure if anyone has built out a fully operational reporting architecture without using SQL on HN. Long live SQL!
Re: Genealogy of Relational Database Management Systems [pdf]
#3This is incredible to see all in one place. I’m preaching SQL to my Org. and it’s only getting preachier over the years, as I see new technologies come and go (OLAP, NoSQL and it’s many variations including Hadoop, Azure Cosmos DB). For an Org. of our size, I’m not sure if these new fads make it any easier. Even if they helped with data streaming, we still are having to move it to a SQL warehouse where we can combine…
I'm kind of amazed that SQL needs to be preached about. It works really well! Just pick whatever flavor works best for your org and go forward.
What would you use INSTEAD of SQL?
Re: Genealogy of Relational Database Management Systems [pdf]
#4This is incredible to see all in one place. I’m preaching SQL to my Org. and it’s only getting preachier over the years, as I see new technologies come and go (OLAP, NoSQL and it’s many variations including Hadoop, Azure Cosmos DB). For an Org. of our size, I’m not sure if these new fads make it any easier. Even if they helped with data streaming, we still are having to move it to a SQL warehouse where we can combine…
I'm kind of amazed that SQL needs to be preached about. It works really well! Just pick whatever flavor works best for your org and go forward. What would you use INSTEAD of SQL?
I've only had contact with DBs during my university years so please bear with me, but at least to me (mostly a systems programmer who played around with functional and logic programming languages) SQL seems, I dunno.. very crude? For instance it seems to me that PROLOG is a lot better at querying/defining relational facts.
Also every time I looked into SQL DBs I felt uncomfortable having to patch together SQL queries as strings and compile them at runtime. Why can't I define a DB schema in my compiled programming language and have it produce a typesafe query that can execute immediately? I know there's wrappers that help you define queries in a typesafe manner, but afaik these still generate query strings in the background.
Re: Genealogy of Relational Database Management Systems [pdf]
#5R:BASE isn't listed, an important PC relational DBMS.
Postgres / Enterprise DB converges towards compatibility with Oracle DBMS.
Re: Genealogy of Relational Database Management Systems [pdf]
#6This is incredible to see all in one place. I’m preaching SQL to my Org. and it’s only getting preachier over the years, as I see new technologies come and go (OLAP, NoSQL and it’s many variations including Hadoop, Azure Cosmos DB). For an Org. of our size, I’m not sure if these new fads make it any easier. Even if they helped with data streaming, we still are having to move it to a SQL warehouse where we can combine…
I'm kind of amazed that SQL needs to be preached about. It works really well! Just pick whatever flavor works best for your org and go forward. What would you use INSTEAD of SQL?
Some people think maintaining bank accounts on Mongo would be a good idea.
ACID, locking, referential integrity, SQL (language flavors and RE DBMSes) aren't appreciated, probably due to a lack of CS education.
Re: Genealogy of Relational Database Management Systems [pdf]
#7Pretty good. Where would the Oracle Lite products go?
Re: Genealogy of Relational Database Management Systems [pdf]
#8Earlier quoted context omitted.
I'm kind of amazed that SQL needs to be preached about. It works really well! Just pick whatever flavor works best for your org and go forward. What would you use INSTEAD of SQL?
I've only had contact with DBs during my university years so please bear with me, but at least to me (mostly a systems programmer who played around with functional and logic programming languages) SQL seems, I dunno.. very crude? For instance it seems to me that PROLOG is a lot better at querying/defining relational facts. Also every time I looked into SQL DBs I felt uncomfortable having to patch together SQL queries…
Prolog isn't a DBMS, it's a functional / logic programming language. It doesn't store tables or operate on relational algebra.
How would you CRUD data DDL, DQL, DML, DCL, TCL against tables (not facts or variables) without SQL? Magic?
And why are you cobbling queries together manually and not using an ORM or library? SMH.
Re: Genealogy of Relational Database Management Systems [pdf]
#9Earlier quoted context omitted.
I'm kind of amazed that SQL needs to be preached about. It works really well! Just pick whatever flavor works best for your org and go forward. What would you use INSTEAD of SQL?
I've only had contact with DBs during my university years so please bear with me, but at least to me (mostly a systems programmer who played around with functional and logic programming languages) SQL seems, I dunno.. very crude? For instance it seems to me that PROLOG is a lot better at querying/defining relational facts. Also every time I looked into SQL DBs I felt uncomfortable having to patch together SQL queries…
Few people, when they say "SQL is amazing!", mean the language.
The language is ok minus, it's usable and isn't a problem center. String parsing isn't expensive enough for anyone to replace, and there are many benefits to the 100% language decoupling it ensures.
What we mean is "RDBMSs are amazing!", and they are. Humanity has spent a lot of resources on their design and evolution, making them into systems that efficiently solve your hard problems years before you first find out you have them.
Re: Genealogy of Relational Database Management Systems [pdf]
#10This is incredible to see all in one place. I’m preaching SQL to my Org. and it’s only getting preachier over the years, as I see new technologies come and go (OLAP, NoSQL and it’s many variations including Hadoop, Azure Cosmos DB). For an Org. of our size, I’m not sure if these new fads make it any easier. Even if they helped with data streaming, we still are having to move it to a SQL warehouse where we can combine…
OLAP isn't a technology and it didn't go away. That's an approach your and many other orgs have been using for decades to do data warehousing. NoSQLs definitely didn't go away.
The need for denormalized data and data warehousing will never go away.