Data modeling issue

[#1]

Hello folks,

can someone please say..what i did is correct or wrong??

please let me know...what i did is correct or not..?

thanks

Venky

[Anonymous]

The corrected version looks much better than the original.  Still there are issues.

1. Instead of using the composite key, I'd rather linked them by ProductID and removed UnitPrice from the Product table.  The reason - price is most likely the attribute of the order detail than of the Product.  Same Product may have different price in different orders.

2. Employee table is a data island - is it intentional?

[#3]

is this correct bro????

[maxgro]

2

there are 2 employee fields but with different names

maybe they are the same?

[Anonymous]

Data model looks reasonable now.

I possibly would join orders and order details in one table - but maybe not...  You can keep it this way of course.

[#6]

do you mean first name and last name?

[#7]

if i join both orders table and order details..i am getting different values..so i didnt join them mov‌

[Anonymous]

Yes, if you join them, you need to take special measures to avoid data distortion because it is one-to-many relation.  You'll be fine without joining

[Anonymous]

I assume maxgro meant EmployeeID in Orders but EmpID in Employees.  You've fixed it already.