jsaacson
asked on
large stored procedure versus small stored procedure
I am trying to determine if it is better to build one large stored procedure with many parameters, or several smaller procedures with fewer parameters. Besides the question of performance, I have a concern about being able to provide feedback to the user to know what is going on if the procedure takes a long time to run. For example, if I wrote the code in vb.net and embedded it the program, I would keep sending messages to a status strip as each step of the process was started and/or completed. I don't know how I can do this with a stored procedure if I had one long procedure instead of several shorter ones.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the last link... this is what u want. Note that the status messages are asynchronous in nature.
ASKER
I have been looking at them and I think it is beginning to make sense to me. I am going to play with this for a while and see how it works.
I appreciate the help you both have given.
I appreciate the help you both have given.
ASKER
There is reusable code, as the process will gather data from the same tables but for different periods (ie current year, prior year).