title: SQL Server Management Studio not showing correct data space of a table
body: <h2>Before</h2>
  
  <p>I had a table with 8 columns. The one that is important here is called <code>SerializedCriteria</code>. It was text column with <strong>a lot of data</strong>. And by a lot of data I mean over <code>37000 strings</code> with length of <code>20-30 kb</code> of text.</p>
  
  <p>Anyway this is how the tabled looked like before:</p>
  
  <p><img src="https://i.stack.imgur.com/pPScG.png" alt="table design before deleting the column"></p>
  
  <p>The size of the table was huge. <code>37218 records</code> with total size to more than <code>1 GB</code></p>
  
  <p><img src="https://i.stack.imgur.com/6Act0.png" alt="table size statistics before deletion"></p>
  
  <h2>Actions</h2>
  
  <ol>
  <li><p>I <strong>deleted the column</strong> since I've moved the criteria to another table.
  I am using Entity Framework Code First migrations for making changes to the database.</p></li>
  <li><p>I <strong>shrink</strong> the database and the file of the database</p></li>
  <li><p>I <strong>restarted</strong> Microsoft SQL Server Management Studio</p></li>
  </ol>
  
  <h2>After</h2>
  
  <p>Of course the column is removed as I intended:</p>
  
  <p><img src="https://i.stack.imgur.com/R0q9L.png" alt="table design after deleting the column"></p>
  
  <p>The problem is that after the above actions the <code>size statistics</code> of the table are <strong>still the same</strong>:</p>
  
  <p><img src="https://i.stack.imgur.com/a2kXU.png" alt="table size statistics after deletion"></p>
  
  <h2>Questions</h2>
  
  <ol>
  <li>Is the problem in Microsoft SQL Server Management Studio or is the deleted column's data is still there?</li>
  <li>How to see the actual size of the table?</li>
  <li>If still used, how to remove free the data used from the column. Do I need to somehow shrink or recreate the table?</li>
  </ol>
  
  <h2>Note</h2>
  
  <p>The screenshots are with different UI because I've took the screens from production database since in my local SQL Server the changes are already done.</p>