SQL Server a lot of Single use objects -


We have a database with approximately 50-60% recompilation, this value [batch request / sec] together with [SQL] Coming / Seconds] comes from

We feel that this value is slightly

If we look at this question: / P>

  SELECT.dll_exec_sql_text (qs.sql_handle) ST WHERE qs apply the. Plan_generation_num & gt; 1 ORDER plan_generation_num DESC  

If you compare it to performance count then we do not have many plan_generation_num, we have the same object of use and why am I trying to understand it ?

There is an application created in our ASP.NET and we always use the parameters that are queryed. We use both SP and SQL-statement in the application, but are always parametida.

The webpage that is running this database again is a very large website, approximately 500 000 pageviews per day and approximately 10 000 requests per minute if this information helps.

We do not have long-lasting questions and indexes and Statistics is in order. This is one of the last things to optimize.

CPU average 15% of RAM is about 100 GB and is the curl used by SQL-server. We use SQL Server 2014 Enterprise.

One thing I started thinking about the beginning. If I have such a SQL statement

  choose seats from windows, cars where wheels = @ vahillas and activate = 1  

Is it The plan is not to be reused, we do not set a parameter on this part: ** and activate = 1 **

How to get any idea about how we are so alone Why use? Calculation on cached plans is approximately 20 000. In comparison, we have around 700 SP 'and many more questions in the app.


Comments

Popular posts from this blog

winforms - C# Form - Property Change -

java - Messages from .properties file do not display UTF-8 characters -

javascript - amcharts makechart not working -