title: Is VARCHAR like totally 1990s?
body: <ol>
  <li>VARCHAR does not store Unicode characters.</li>
  <li>NVARCHAR does store Unicode characters.</li>
  <li>Today's applications should always be Unicode compatible.</li>
  <li>NVARCHAR takes twice the amount of space to store it.</li>
  <li>Point 4 doesn't matter because storage space is extremely inexpensive.</li>
  </ol>
  
  <p>Ergo: When designing SQL Server databases today, one should always use NVARCHAR.</p>
  
  <p>Is this sound reasoning? Does anyone disagree with any of the premises?
  Are there any reasons to choose VARCHAR over NVARCHAR today?</p>