• John Mitchell-245523 - Monday, November 20, 2017 3:30 AM

    davidvarga086 - Monday, November 20, 2017 3:22 AM

    If one of the calculations change in a stored proc I would have to fix it in three places instead of 1 (monthly, weekly, daily)

    Not if you modularise the calculations with stored procedures or functions.

     I would have to create 350+ new stored procedures for weekly plus 350+ for daily. 


    I don't understand. Why 350?

    John

    modularise? I'll give you an example. One of our calculations gets the average number of tickets closed on a monthly bases. If I do it on a daily bases then average it again for weekly or monthly that would be inaccurate.
    If I would wan't to fix it to a format that would be good for all three I would have to fix a lot of stuff not just the stored procedures end user stuff as well like (reports on pages, we have an app that creates a word document with charts and tables gathered from this and mail subscriptions of some of the calculations) and go through a lot of red tape.

    356 is the amount of calculation types that we currently have but the number will go higher in the future. all the calculations are in separate stored procedures, the reason for that is that each one of them can connect to different linked servers and we don't always need to run all of them sometimes running 30 is enough(so we lessen the load on the linked servers), but sometimes all of them have to go. and it's easier for maintenance.