title: Normalize or denormalize varbinary in large table?
body: <p>I am developing a system involving a 500  GB SQL Server Database.</p>
  
  <p>Query performance and storage complexity are of concern in this scale.</p>
  
  <p><b>Question:</b> The table with most of the records contains a VARBINARY(1500) field which is NULL about 90% of the time. Is it better to normalize this field into a separate table or keep as-is?</p>
  
  <p>Performing actual test would take a lot of time, hoping to save time by asking here first.</p>