seo.reputeinfosystems - Thursday, November 23, 2017 12:01 AMI am currently working on a monitoring tool where the database "architecture" was driven by the application development and objected-oriented methodologies were applied to the database resulting in multiple layers of indirection with multiple nested views, numerous scalar functions, procedurally coded triggers and a rat's nest of stored procedures. And they wonder why they have performance issues!
That's the way it was at the company I currently work for and one previous. We also had cursors everywhere for that one previous. They had also hired a contractor that advised them to replace the cursors with <major face palm><head-desk><head-desk><head-desk> temp tables and While loops and they spent a hell of a lot of money doing just that. It took substantial time (measured in years) and effort to clean most of that up and the company moved to another state before we could complete it. I did "follow" their efforts through some of the people that made the move with the company and it only took them a couple of months to revert back to those same poor practices because most of the developers they hired locally after the move were of the same gene pool as the originals. My only joy in that is it serves them right for moving to another state.
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Change is inevitable... Change for the better is not.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)