• @LutzM

    Until the process change, i think that all in one table product case was a good choice, and if my company doesn't had changed the process I never had thought in redesign...

    I think that's easier to make a:

    SELECT * FROM Table

    than:

    SELECT * FROM Table1 INNER JOIN Table2 ON ... INNER JOIN Table 3 ...

    But now the process has changed and i need to adapt to apply the changes, so i need to go through the normalization process, but are some doubts, btw that's the point of this thread, that i need to clarify to make a good and flexible schema this time...

    For example I don't see how i would design the tables to make the query to handle the situation that i described in my last reply, the skipping part of departments, the resulting JOINS, and some other issues that i don't recall right now...