August 12, 2013 at 10:01 am
I have some jobs running a few scripts that populate several reports. I've run these reports reports two ways:
1. Each report has their own procedure (around 25 procedures).
2. All of the reports share a few procedures (around 5 or 6).
I'm actually finding it optimal to run them from their own procedure. (This particular project will not get any bigger). However, in many of the same places the code is basically the same. Is there a good (or easy) way to keep up with the general source code (I'm not sure if that is the right term). Basically, I'm hoping for an easier way to manage updates to the general code that is duplicated across the procedures. Any help is appreciated.
August 12, 2013 at 11:37 am
It entirely depends on the code that you have as to how much can be reused, but you may want to explore the use of functions and calling those functions in each code piece?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply