Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Should I move to NoSQL? (big data)

I'm currently researching a very large table (~100 million rows, 35 columns), it's currently stored in SQL db, but the queries I'm running (and they're various) run very, very slow.. so I get it I should probably move to NoSQL db. question is:

  1. How can I tell which (NoSQL) db is best for me?

  2. How can I move my current SQL table to the new NoSQL scheme?

OR should I stay in SQL and just fine tune it?

A few more details: rows will not be added/removed, this is historical data and all of the analysis will be done on that table. plan to run various queries on it. data is numerical.

like image 389
Lior S Avatar asked Dec 08 '22 10:12

Lior S


1 Answers

I routinely work with a SQL Server 2012 table that has 900 million rows. This table has rows being added to it about every 2 minutes with a total of about 200K per day. I can query this table and get rows back in a couple seconds (using the clustered index / PK). I can also query on one of the other indexes and get results back in seconds or less.

So, it's all a matter of making sure your indexes are set up correctly, AND BEING USED!! Check your queries against the query plan being generated and make sure seeks are being done.

There could be good reasons for moving to NoSQL, or something similar. But moving to NoSQL because you think you can't get good performance in SQL Server, before making sure you've done everything you can do to improve performance first, is not a good reason.

like image 129
Randy Minder Avatar answered Dec 11 '22 10:12

Randy Minder