From: Johan De Meersman Date: February 16 2011 11:41am Subject: Re: Limit of Mysql List-Archive: http://lists.mysql.com/mysql/224431 Message-Id: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=0015174be68cad04b5049c64c2c2 --0015174be68cad04b5049c64c2c2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mostly correct - save for pointer sizes and such, but it's pretty hard to reach those. SQL vs NoSQL is not a matter of data size - plenty of fud is being spread about NoSQL, for some reason - but a matter of access patterns. Without knowing what you need and how you design, that question can't be answered. On Wed, Feb 16, 2011 at 8:48 AM, Reindl Harald wrot= e: > there are no hard limits as long your hardware ist fast enough > > * memory, memory and agin: memory > * disk-speed > * cpu > > Am 16.02.2011 06:04, schrieb Adarsh Sharma: > > Dear all, > > > > I want to know the upper limit of mysql after which Mysql-5.* fails to > handle large amount of data ( 100's of GB > > or 100's of TB's ) . After which we have to move to some NoSQL database= s > ( Hadoop, Hive , Hbase). > > > > Currently we have 100 of GB's data in Mysql -5.1 RDBMS. > > > > Is anyone has some experience of moving from these open -source databse= s > ( Mysql, Postgresql ) to some mechanism of > > handling data in file systems. > > > > Please share the views. > > > > > > > > Thanks & best regards, > > > > Adarsh Sharma > > > > > > > > -- > > Mit besten Gr=FC=DFen, Reindl Harald > the lounge interactive design GmbH > A-1060 Vienna, Hofm=FChlgasse 17 > CTO / software-development / cms-solutions > p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 > icq: 154546673, http://www.thelounge.net/ > > --=20 Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel --0015174be68cad04b5049c64c2c2--