When is the size of the database call more expensive than the frequency of calls? -


Can anyone give me a relative idea when trying to hit the database several times to capture the small query results? Understand the large number of rows and raising questions on it?

For example, if I return 2,000 results and then I have additional questions on those results that take 10-20 items, would it be better to cache the results of 2000 or 10 or 20 Will every time the database hit each set of results? Other answers are correct here - RDBMS and your data are important factors. However, another important factor is that it is the most important factor in the process of using this type of data.

DataSet and subkeys on it as it turns, keep that data up to date and Choosing subsets has really slow motion in leaving the data in the database.

So my advice is: This is the easiest way, first see the profile and see if you have to adapt to the display.


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -