high Compilations/sec value

From: mm (postto_at_news.com)
Date: 10/25/04 

Date: Tue, 26 Oct 2004 08:18:36 +1300

Hi,

Would someone please explain what causes a high "Compilations/sec" count?

Is still caued by stored procedures not being cached and not enough memory
alloacted to SQL Server.

Thanks

Relevant Pages

  • Re: So, anyone asked about Win64 at Borcon?
    ... Since scalability and large memory access ... CLR stored procedures. ... will be slightly faster in extended stored procedures than CLR stored ... procedures for each processor type you want to run your SQL server on. ...
    (borland.public.delphi.non-technical)
  • Re: Table variables
    ... > I am working with a system that uses quite a lot of stored procedures ... > database server quickly rises to close to 2 Gb. ... The amount of memory ... > used by sql server is limted but as soon as the memory reaches the ...
    (microsoft.public.sqlserver.server)
  • Re: Performance degrading over time
    ... If you have lots of other things than SQL Server on the same box you might ... leave enough memory for them to operate properly minus about 200MB. ... > performance happens across different stored procedures, ...
    (microsoft.public.sqlserver.clustering)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)
  • Re: FTS Performance in SQL 2005
    ... we had no end of problems with SQL FTS. ... Looking for a SQL Server replication book? ... The Memory Usage and VM Size never increase over about 65 MB and 20MB. ... cost relative to the whole batch, ...
    (microsoft.public.sqlserver.fulltext)