title: Is there a downside to creating a table for each import to save time upon search?
body: <p>I'm making a web application with a very specific, albeit fairly simple set of requirements.</p>
  
  <ol>
  <li>The user must be able to upload 100+ spreadsheets, each containing 40-200k rows.</li>
  <li>The user must be able to perform near real-time searches (&lt; 0.5 seconds) on <em>a specific spreadsheet import</em>.</li>
  </ol>
  
  <p>Because the application does not need to search <em>all spreadsheets</em> a user has uploaded, but rather just a single spreadsheet designated beforehand, it seems that the most efficient way to do this would be to upload each spreadsheet as a database so that we only need to run through 200k hands at most as opposed to running through a database of potentially millions of rows by way of a pivot table, for example.  Am I thinking about this correctly?</p>
  
  <p>My plan would be to make a database in the form of Username_SpreadsheetName and to simply import into that database and select from it when it comes time to search.</p>
  
  <p>I know this works and it works well, but it seems really quick and dirty to me. Wondering if there is a more clean way to achieve a similar level of efficiency that I'm not considering.</p>