title: Licensing of LocalDB on a small commercial product
body: <p>As LocalDB seemed to be a nice and simple relational solution for a small amount of data, we thought it would be a simple yet effective solution for our relatively small commercial product.</p>
  
  <p>Now, as the product is close to its release, we are concerned whether or not it would be appropriate to use it on client's workstations or there should be any changes. We are mainly concerned about issues like licensing.</p>
  
  <p>After doing some research, I came to the following conclusions:</p>
  
  <ol>
  <li>LocalDB <a href="https://softwareengineering.stackexchange.com/questions/92948/what-is-needed-to-deploy-an-application-that-uses-microsofts-new-localdb">is a part of the SQL Local Express</a>.</li>
  <li>SQL Express <a href="https://stackoverflow.com/questions/2011716/can-i-use-free-sqlserver-express-in-commercial-app">can be used in commercial apps</a>.</li>
  </ol>
  
  <p>Therefore it seemed logical that LocalDB could be used in production without licensing issues. Considering though that licensing can be a very strict field, we still have concerns on this.</p>
  
  <p>Apart from that, we are wondering if there are there any other big drawbacks on using LocalDB in production, considering our project contains a small amount of data and not the requirement of any need for centralized deployment.</p>
  
  <p>So, the main question is, are we allowed to use LocalDB in a commercial product and, if yes, are there any big drawbacks to this usage?</p>