Database Design Issues - Clarification Required

Question

im designing a database using SQL Server 2005

Our main concept is to import XML feeds from suppliers.

another provider may have a different view of the data

the problem is that I need to create a table to store imported information

some of the columns are fixed, which means that all products of the supplier must have similar data coming from the feed, for example: name, code, price, status, etc.

but some products have additional data, for example

one product is a color property another cannot.

What is the best way to store such a script in a database.

should I create a table for required columns and other tables to accommodate an optional column.

or should I first list the entire column and put them in one table. (there may be many null values)

Thousands of products and database speed are very important.

we will do many product comparisons with different suppliers

our database will be similar to www.pricerunner.co.uk

I hope I explain the concept well

Answer 1

Depends on how you want to access it.

As you say, speed is important - but what are you going to do with these extra, optional, bits of information? Do you need to store them at all? Assuming what you are doing, how often do you need to access them?

, , , , . , , .

, , , , , , . ( ) - , , - , , .

. , .

, , , , () , , .

, , . , , , . .

Answer 2

( ). , .

, , , , .. ( ), .