Mohit K. Gupta (11/4/2013)
When I wrote this article, I didn't take many things into consideration. However the primary reason for article was to provide normalization, which made it easier for administrative staff to manage the administrative tables from within the system.
Yes, you got that right 😉 Thanks for the article, though, because it is a very nice example of exactly "normalization in the background". Newbies searching for inspiration only needs to disregard the use of views with user-defined functions - and cursors... That is the top three performance-killers, all in one go. Not a matter here, but definitely not scalable.
And then the article needed to finish by addressing the update/delete routine "by many people" which is mentioned in the beginning. The whole purpose of creating 5 objects to replace 1 could do with some emphasizing: That 3rd vendor application won't fail due to errors in the back-end maintenance, once a new front for maintenance has been written. The normalization described is mandatory for that to succeed.