May 27, 2011 09:43 AM|atconway|LINK
Answer to #1: If you are referring to (1) or (2) tables in the database
then this is a decision to normalize further the schema to make (2) tables or (1). If you believe there are several instances where it makes more sense to have the data normalized into (2) different tables, then I would go that direction and just use a JOIN
when appropriate in SQL to seamlessly bring that data back together. It is really more of a database question that one of coding, because by the time the app receives that data via whatever access method you choose (ADO.NET, etc) it can be in what ever form
you want it to be for your app and does not need to resemble the database structure at all.
Answer to #2: Use FILESTREAM in SQL Server 2008. The following (2) links will help explain it:
Hope this helps!