InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 03:52:05 GMT20http://www.sqlservercentral.com/Forums/Topic1372547-373-1.aspxThanks again for the response.I forgot to mention that I have to get this thing all the way to 3NF.There's no employee role in your suggestion.I've attempted to go a step further and get it to 2NF and I got:[b]week[/b][b]site[/b][b]day[/b][b]employee[/b] role[b]timeSlot[/b][u]site [/u][u]week [/u][u]day [/u][u]employee[/u] timeSlot[u]employee [/u][u]week [/u]totalHoursBold attributes are assumed to be IDs.Underlined ones are foreign keys.As you see I'm still confused. The set of attributes is so varied that I'm tempted to jump in and split them up immediately. Unfortunately I have to prepare the formal solution and what should be added in 1NF is supposed to be in 1NF, what in 2NF in 2NF. Else I'll lose some points while being graded :)Thank you again for your time :)Mon, 15 Oct 2012 10:40:28 GMTzesralem_siehttp://www.sqlservercentral.com/Forums/Topic1372547-373-1.aspxOh I see, OK, I don't think 1 is correct, with {day} there you'll have non unique week site keys, or am I jumping past 1nf.. IMO, I think it should be[u]week site day timeSlot* employee*[/u][u]Week day employee[/u] sick[u]Employee week[/u] totalhoursIts getting a little into 2nf I think though.. but you can still break out further since employee does not depend on week site day etc.. so possibly OK.Mon, 15 Oct 2012 09:40:31 GMTfoxxohttp://www.sqlservercentral.com/Forums/Topic1372547-373-1.aspxThanks.That thing exactly confuses me, because trying to do top - down approach for this case I know I will need a separate table for almost every attribute here.But I'm not really quite sure how to go about bottom-up approach. I know the rules of normalization, and that should be enough, but still...UNF: [u]week [/u] [u]site [/u] day timeSlot* employee* role* sick* totalHrs*Let me try do the 1NF (I should break out repeated groups to form new group and include original key as a foreign key), so:1NF:1) [u][b]week [/b][/u][u][b]site[/b][/u] day (should I put the day attribute here? the data itself does not repeat in the form)2) [u][b]employee[/b][/u] [u]week [/u] [u]site [/u] timeSlot role sick totalHrsWhat do you think about it? Is that ok?Mon, 15 Oct 2012 03:50:15 GMTzesralem_siehttp://www.sqlservercentral.com/Forums/Topic1372547-373-1.aspxIf you take a look at the Microsoft example database called AdventureWorks, it has a very similar structure to what you're looking for:[url]http://msdn.microsoft.com/en-us/library/ms124438%28v=sql.100%29.aspx[/url]Specifically look at the HumanResources.Shift, HumanResources.EmployeeYou need separate tables for Site (ID name location purpose), Employee (ID name occupation), Day (ID, Name), EmploymentRole (ID, rolename), TimeSlot(ID Start and end times - no dates), Sick(Maps Timeslot & Employee), ShiftRecord (Maps EmpID, DayID, TimeSlotID, RoleID)Then use excel to link to these tables with dropdown selection list (MyList function).Mon, 15 Oct 2012 00:44:29 GMTfoxxohttp://www.sqlservercentral.com/Forums/Topic1372547-373-1.aspxHey guys, I have some problems with normalizing the data.Could you take a look at this filehttp://speedy.sh/YtK9G/example.xlsxThese is the list of attributes: [u]week[/u] [u]site[/u] day timeSlot employee role sick totalHrsWeek and site will be a compound key.A lot of things confuses me here so I'd really appreciate your help. Thanks in advance :)Sun, 14 Oct 2012 17:17:58 GMTzesralem_sie