[dba-Tech] NOSQL goes SQL?

On 2013-02-25 10:22 PM, Jim Lawrence wrote:
> Hi Stuart:
>
> At the risk of being repetitious, NoSQL is not trying to replace SQL. The
> only reason similar products Map Reduce are around because SQL can not do
> the job of managing huge data.
>
> SQL databases handles up to a million pieces of data while NoSQL databases
> handle billions of pieces of data.

MySQL handles loads like that. The DB needs to be structured correctly 
according to whether it's mainly OLTP or OLAP, of course, or split into 
OLTP and OLAP instances. It might also benefit from partitioning, or 
from deployment of a MySQL Cluster.

PB

-----

>
> http://gigaom.com/2013/02/21/sql-is-whats-next-for-hadoop-heres-whos-doing-i
> t
>
> Just think if the UI to NoSQL databases was really easy there goes those big
> bucks for the techs that manage these ugly monstrosities now get. ;-)
>
> Jim
>
> -----Original Message-----
> From: dba-tech-bounces at databaseadvisors.com
> [mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
> Sent: Monday, February 25, 2013 3:21 PM
> To: Discussion of Hardware and Software issues
> Subject: [dba-Tech] NOSQL goes SQL?
>
> So much for NOSQL being the answer to life, the universe and everything.
>
> http://www.theregister.co.uk/2013/02/25/hortonworks_stinger/
>
> Hortonworks has unveiled the Stinger Initiative, a project to make Hadoop´s
> Hive data
> warehouse friendlier with SQL and faster.
> ...
>   Hadoop is a open-source implementation of Google´s MapReduce and a NoSQL
> system.
>
> However, the NoSQL crowds realised they need to make their architectures
> work better with
> SQL-like tools used by businesses in the real world.
> ...
> According to Hortonworks, Stinger will make Hive "a more suitable tool for
> the decision
> support queries people want to perform on Hadoop".
>