Eric Evans about SQL obsession

Copyright notice: This is a quotation taken from the episode #226 of Software Engineering Radio podcast, available at http://www.se-radio.net/2015/05/se-radio-episode-226-eric-evans-on-domain-driven-design-at-10-years/. The audio recording is licensed under the terms of Creative Commons 2.5 license, which allows redistribution of the copyrighted material. All rights belong to the original copyright owner.
-------------------------------------------------------------------------------------------------------------------------------

48:03
One of the biggest handicaps that we had for a long time, is this obsession with everything being stored in a relational database. Data in a relation database has to be structured in a certain way. In the days when objects were dominating, the relation databases were still the dominating kind of database, so we used all that mappers - Object-Relational Mappers - of course, people still use this (I said if it was in the past), and the people will talk about the impedance mismatch. What's the impedance mismatch? This says that fundamental construction's structure of object is different from the relational table or set of tables. The way they relate to each other is different. The trouble here - I think it was Eric Mayer who had made this point - when we saying NoSQL, we should make "No" being an acronym: "Not only". We should say: "Not only SQL". And his point was that the program isn't a relational database, which is a brilliant thing, it's a wonderful powerful tool! But when you use them for EVERYTHING, then you... in kind of data that doesn't fit into them, it isn't in the right shape, and you have to twist them into that shape. But when you're dealing with the problem that fits them... they are fantastic tools. But if we are using them for everything, you know - it's hard to find a tool that works for everything.