Geek Answers Handbook

Is it possible to improve cached SQL server performance?

What is the most common and easiest speed solution for SQL Server 2008R2 database and .Net 3.5 application.

We have an application with the following attributes:
- a small number of simultaneous clients (~ 200 in MOST).
- complex mathematical operations on the side of the SQL server
- we imitate something by the oracle of security at the row level (thus, using tvf and storedprocs instead of directly querying tables) The main problem is that users perform a large number of updates / inserts / deletes / computing, and they worry because they need to wait for the pages to reload while these actions are completed.

Points requiring clarification are as follows:

  • What happens faster: returning the entire data set from the SQL server and performing mathematical functions on the C # side or performing calculation functions on the SQL side (thus, not returning additional columns). Or does it depend only on the equipment?
  • Will caching improve performance (for example, if we add redis cache). Or are caching solutions only possible for a large number of clients?
  • A good practice is to pre-compute some data and store it somewhere in the database (so when the user asks for it, it will already be calculated). Or is this what caching is supposed to do? If this is not a bad practice, how can I configure the SQL server to perform calculations when resources are available?
  • , , - ?

.

+5
1

, , . , SQL- , , .

, , , /, , . , , / , . - .

, . ? , , , SUM/AVG , SQL, , , , #. ! , , , :). , , , , . , , , , .

, , , , , , , .

- SQL Profiler, stmt: , , /io/cpu .

!

+7

More articles:


All Articles