norbert.manyi (10/3/2012)
All the developers are on both SQL and .Net, so we will not have those kind of problems.Most of my concerns are regarding keeping everything in one place, and as clean as possible.
So, at the moment, I can say I'm confused 🙂 I am aware of the speed gained by keeping everything in optimized stored procedures, but in the same time, I would like to maintain flexibility to make changes in BL faster, and with less modifications.
From what you've desribed, I think a view would provide the business logic encapsolation you need. As far as the employee table itself, it would be useful to have active_date, inactive_date, and status_code columns indicating the timeframe and reason for the employees status.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho