• I guess I always look at a problem as always having a solution. I may not have the answer but I believe it is out there. Just last week we had some major slowness in our production processing, pulling data from a data repository into our warehouse. One process ran for 8 1/2 hours, another 3 1/2 hours. I was very familiar with the 3 1/2 hour process, since I wrote it. So I focused on the 8 1/2 hour process, I made some coding changes, and it ran in just over an hour the next night. While changing that coding we discovered a process from another team was doing 98 billion reads against this repository. So after it was canceled and the code fixed I thought "well I don't need to look at the job I wrote then." But the next night it still took 3 1/2 hours. So I did some research and found I was not joining two of the tables in the most efficient way. I changed the joins and the next night... 2 minutes. WOW, I couldn't believe it. Now to clarify I had written the original code about a year ago when we first started working with this repository, and there was a lot less data. So, yes there was a solution to the problem and I learned never to assume "it can't be my code". 🙂

    -------------------------------------------------------------
    we travel not to escape life but for life not to escape us
    Don't fear failure, fear regret.