Basic table relationship question

Question

Just getting started working with primary and foriegn key relationships.  I have a main table called fruitPicking and one of the columns is fruitID (a foriegn key linked to a primary key in a table called fruit).  Anyhow for a single row
in the fruitPicking table I need to store more than just one fruitID for a specific day, for example apples and oranges may have been picked that day so for the row in the fruitPicking table I would want to include the foriegn key for both an
apple and orange for the same date (date being another field in the fruitPicking table).  Is it correct to just use two rows in the fruitPicking table with the same date, one row with the foriegn key for apple and the next with the foriegn
key for orange? Thanks.

Answer 1

Hi Svt44cobra66,
We can create a unique constraint by using SQL Server Management Studio or Transact-SQL to ensure no duplicate values are entered in specific columns that do not participate in a primary key. When creating a unique constraint, a corresponding unique index will
be created automatically. Here is a document about how to create unique constraints:
http://technet.microsoft.com/en-us/library/ms190024.aspx.
Reference:
What is the difference between primary, unique and foreign key constraints, and indexes?
Regards,
Heidi Duan
Heidi Duan
TechNet Community Support