title: SQL vs NOSQL: Which to use for this schema?
body: <p>I've got an upcoming project and I can't decide whether to stick with SQL or switch over to NoSQL. It's basically a reporting system with the main interface being reporting on the data entered in by users.</p>
  
  <p>Here's the schema I've got mapped out:</p>
  
  <p><img src="https://i.stack.imgur.com/CIuMW.png" alt="enter image description here"></p>
  
  <p>Because this schema is so nested, I started thinking about NoSQL.  With SQL, I'm afraid I'm going to have a crap-ton of joins to get to the bottom of the tree (the Record model).</p>
  
  <p><strong>My concerns, though, are two-fold:</strong></p>
  
  <ol>
  <li>I'm only just starting to get into NoSQL and I'm worried my
  knowledge may limit me because of the tight timeframe.</li>
  <li>Although creating data at the bottom of the tree will probably be relatively simple, I'm worried that it may be hard to report on without getting into some heavy map/reduce stuff (that I have zero experience with)</li>
  </ol>
  
  <p><strong>My question:</strong>
  Given my concerns, do you think this schema -- because of how deeply nested it is -- lends itself more to NoSQL? If so, do you think the reporting on the "records" will be difficult?  </p>
  
  <p>I realize that it may be difficult to answer these questions without more info, so please let me know what other info may be helpful in coming up with an answer.</p>
  
  <p>Thanks in advance for your help!</p>