Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-07-21 : 09:42:58
|
| Gary writes "I have a client with a large C# system which accesses a SQL server database.I am in the processing of optimizing the system/database for them.The original designers made data objects of everything in the system.SQL call and stored procedure called are encapsultated in two routines.Timeouts are the only parameter that they are setting.In most cases the SQL or stored procedure return more than 20 rows and in some slow running applications they can return as many as 200 rows to populate grids or calculate totals for summary screens.The question is if I enable client side caching and make the number of rows cached a fairly small number like 10 rows to allow for older client machines which may have less memory.Will I decrease the number of network requests/transmissions roundtrips for the queries returning a larger number of rows.Typically once the SQL has been executed the programs are ready use all the at once to populate grids calc totals etc...I have been unable to find a clear enough description of client side caching to answer this question for me." |
|
|
|
|
|
Client Side Caching