@Toby Harman
More flexibility and the ability to change the workflow more easily?
- True
Just to be capable of handling future changes in the workflow, like this one that I'm dealing now, and don't need to redesign the tables...
A reduction in the number of columns in your table?
Not the main goal, but has to be reduced by the normalization. Like i wrote before, i put all in the same table because i was learning the business process and developing at the same time, so the table was built incrementally without any thoughts in the possibility of workflow changes, but now i have to change this. I could easily add some more columns to handle the new department, but if in the future the process changes by reducing the number of departments then i can't just remove the columns...
we get paid the princely salaries
Not here, i must do the job of a bunch people (analyst,programmer, database architect, database administrator, tester), and only get one poor salary... :ermm:
About the queries, my only problem it's to put the hands again, in some complex and complicated queries that i had created... 😛