title: moving from sql server to cassandra
body: <p>I have a data intensive project for which I wrote the code recently, the data and sp live in a MS SQL db.  My initial estimate is that the db will grow to 50TB, then it will become fairly static in growth.  The final application will perform lots of row level look ups and readings, with a very small percentile of db write backs.</p>
  
  <p>With the above scenario in mind, its being suggested that I should look at a NoSQL option in order to scale to the large load of data and transactions, and after a bit of research the roads leads to Cassandra (while considering MongoDB as a second alternative)</p>
  
  <p>I would appreciate your guidance with the following set of initial questions:</p>
  
  <p>-Does Cassandra support the concept of store procs?</p>
  
  <p>-Would I be able to install and run the 50TB db on a single node (single Windows Server)?</p>
  
  <p>-Does Cassandra support/leverage multiple CPUs in single server (ex: 4 CPUs)?</p>
  
  <p>-Would open source version be able to support the 50TB db? or would I need to purchase the ENT version?</p>
  
  <p>Regards,
  -r</p>