• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

Specific SQL Procedures

I'm designing a new high volume database from scratch and was planning to have very specific SQL stored procedures.  I want lean logic that a particular application (ASPX) section or two will own.  The idea is to get away from these jack-of-all-trades procedures.  How will using many smaller procs affect performance? (We have a large number of concurrent users...250+ per minute connecting)
1 Solution
Well, honestly...it depends on how they are written.  There really isn't going to be too much of a performance difference between a well written longer proc vs well written shorter procs.  I prefer the shorter procs because its easier to modularize logic...

Its a good idea to try to minimize the amount of times you have to hit the server....so, you could have one procedure that calls lots of other procedures...that way you don't have to make many proc calls that travel over the network to hit the db.  Does that make sense?
Phil5780Author Commented:
Great, thats what I had been thinking to do.  Thanks for the input:)

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now