title: Store dimensions (along with image) in database columns?
body: <p>I must store my images in varbinary(max) fields in a SQLServer 2008 database (file system is not an option in my environment).</p>
  
  <p>I'd like to be able to set image and height properties on HTML image tags when I serve these up (in my MVC2 app) and do different things in a gallery depending on portrait vs landscape orientation. </p>
  
  <p>So, from your experience, would it be worth the hassle (and de-normalization?) to  store this information in separate columns of the database, or is just cheap enough, performance-wise, to grab height &amp; width &amp; calculate orientation on the fly?</p>