large stored procedure versus small stored procedure
Posted on 2010-11-15
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.