SQL Databases: Model Ts for 2010
November 11, 2009
I have been increasingly nervous about Dr. Codd’s beautiful baby, now getting close to Medicare qualification. The knock against SQL databases is that these systems can take quite a bit of work to get in shape for big data. If you want more detail about the limitations of SQL databases, navigate to Adam Wiggins “SQL Databases Don’t Scale”. One of the most interesting comments in the article, in my opinion, was:
So where do we go from here? Some might reply “keep trying to make SQL databases scale.” I disagree with that notion. When hundreds of companies and thousands of the brightest programmers and sysadmins have been trying to solve a problem for twenty years and still haven’t managed to come up with an obvious solution that everyone adopts, that says to me the problem is unsolvable. Like Kirk facing the Kobayashi Maru, we can only solve this problem by redefining the question.
My answer is different data management systems: Aster Data, Exalead, InfoBright, or similar next generation systems.
Stephen Arnold, November 11, 2009
If you think anyone paid me for stating the obvious, you, dear enforcement official, are wrong.
Comments
One Response to “SQL Databases: Model Ts for 2010”
-
- Subscribe to Beyond Search
Feature archive
News archive
-
SQL was designed as a efficient and reliable method of managing the data transaction; though even with all the enhancements it has never proven to be a the appropriate candidate to handle and manipulate big data.
SQL not only needs to scale and grow with the data; but also how users ask questions; which yes leads to different methods of storing and accessing data, along with getting the logic closer to the data.