title: Why doesn't SQL Server support unsigned datatype?
body: <p>I am specifically thinking about unsigned <code>int</code>.  </p>
  
  <p>Here is a practical example: what do you do when your identity column maxes out? It's possible to either go <code>BigInt</code> (8 bytes storage instead of 4) or to refactor the application to support negative integers, and even to create your own rules as indicated in <a href="https://stackoverflow.com/questions/306291/4-byte-unsigned-int-in-sql-server/306300#306300">this answer</a>; neither of those options are optimal.  </p>
  
  <p><code>UInt</code> would be an ideal solution, but SQL Server does not offer it (where MySQL does).</p>
  
  <p>I understand that unsigned datatypes are not part of the SQL standard (SQL-2003) but still seems like a waste to me.  </p>
  
  <p>What is the reason of not including these (in SQL Server or in the standard)?</p>