topic Re: Data modeling issue in QlikView

Data modeling issue

Fri, 26 Jun 2015 22:43:01 GMT

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

Re: Data modeling issue

Anonymous — Fri, 26 Jun 2015 23:02:31 GMT

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?

Re: Data modeling issue

Fri, 26 Jun 2015 23:07:22 GMT

is this correct bro????

Re: Data modeling issue

maxgro — Fri, 26 Jun 2015 23:07:42 GMT

there are 2 employee fields but with different names

maybe they are the same?

Re: Data modeling issue

Anonymous — Fri, 26 Jun 2015 23:16:26 GMT

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.

Re: Data modeling issue

Fri, 26 Jun 2015 23:37:10 GMT

do you mean first name and last name?

Re: Data modeling issue

Fri, 26 Jun 2015 23:39:21 GMT

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

Re: Data modeling issue

Anonymous — Sat, 27 Jun 2015 01:44:36 GMT

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

Re: Data modeling issue

Anonymous — Sat, 27 Jun 2015 01:46:14 GMT

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