Francisco Tapia
fhtapia at gmail.com
Thu Mar 16 10:21:51 CST 2006
As with all things, it depends... If you are doing a lot of searches in the back end for specific gui display, then it makes sense to do something similar to what you are doing. however if certain portions of your screen will not draw until a user clicks on them, it may make more sense to break some of the calls up, so that each call can be snappier, plus you don't make the backend work more than it should.... On 3/16/06, Species 2175 <accessdsql at yahoo.com> wrote: > hi group, > > I'm using SQL Server 2000. > I've developed an application that uses a lot of sp's. > To make this easy for the FE created 4 stored procedures that call 15-35 other sp's. > > e.g.: > create stored proc usp_DoSomething > as > begin > exec usp_DoSomething1 > exec usp_DoSomething2 > exec usp_DoSomething3 > exec usp_DoSomething4 > end > > Is there a performance penalty for this way of working? > Eg in stead of calling/executing each sp on it's own? > > Regards, > > Sander > > > -- -Francisco http://pcthis.blogspot.com |PC news with out the jargon! http://sqlthis.blogspot.com | Tsql and More...