Overhead of Multiple SQL Calls
From: John Smith (js_at_no.com)
Date: 03/01/05
- Next message: Geir Holme: "The name of Scheduler 3."
- Previous message: Craig: "Re: Strange problems accessing SQL server with windows 2000 windows authentication. Please help :)"
- Next in thread: Michael C#: "Re: Overhead of Multiple SQL Calls"
- Reply: Michael C#: "Re: Overhead of Multiple SQL Calls"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Mar 2005 16:17:11 -0500
Hey folks,
I've got a client server C# Windows Form app that communicates with a SQL
Server database backend. The number of users is less than 50.
I'm wondering what the difference in overhead is when say:
a) A Stored Procedure is called ten times, returning 1 record each time
VS.
b) The same Stored Procedure is called once returning 10 records
Due to connection pooling I would think the overhead is somewhat negligible,
especially when there's less than 50 users. I know option 'b' would be the
preffered method when it comes to database communication, but is there
really a BIG difference between the two when dealing with this few users?
Thanks!
(also posted on windows.forms newsgroup on Feb 25 with no response)
- Next message: Geir Holme: "The name of Scheduler 3."
- Previous message: Craig: "Re: Strange problems accessing SQL server with windows 2000 windows authentication. Please help :)"
- Next in thread: Michael C#: "Re: Overhead of Multiple SQL Calls"
- Reply: Michael C#: "Re: Overhead of Multiple SQL Calls"
- Messages sorted by: [ date ] [ thread ]