Relatively small images like that I would store in varbinary(max) column type.
For bigger images you can consider FILESTREAM that stores images on a filesystem but makes it transparent for application. See http://www.infosys.com/microsoft/resource-center/documents/sqlserver-filestream-blobs.pdf

>
>I know this topic has been put out here already on the UT, but I am in the process of designing a database that will require an image of an item stored (or associated) with a database table record. I would like to have some background information on the pros and cons of storing the images in the database versus storing the path of the image on a file system in the table (and/or other options).
>
>Some information to consider is that I will be writing a web application that should display the image of the item on the web form when an item is selected for viewing or editing and would also have an edit form to allow the user to 'attach' an image to the database record from their workstation.
>
>TIA
>
>Bob