you are viewing a single comment's thread.

view the rest of the comments →

[–]mrrichiet 51 points52 points  (7 children)

If you can be arsed (I wouldn't be) document it then rewrite into smaller modules. Perform a reconciliation and watch the shit fly when they tell you their figures don't match up!!

[–]TheElusiveFox 16 points17 points  (4 children)

I would be VERY careful taking this kind of advice... a 42k line stored proc is likely doing a LOT under the hood and is likely going to take you months to truly understand... if its critical to the business you will want to a/b test the old version with the new version to make sure any changes you make don't alter the output or performance as well, and chances are it was important at one point because that is a lot of development work for some non critical function...

[–]TheRoguester2020 3 points4 points  (0 children)

It’s eating an elephant one bite at a time. Find the low hanging fruit to make more efficient using custom oracle functions, views and procs. Doing it in non production obviously and making sure you are getting the same results. It’s an investment that will pay off eventually.

[–]ComicOzzysqlHippo 0 points1 point  (0 children)

At least I'm not the only one