Compilation/sec is more on production where recompilation / sec is zero

Hot Topic

Adding Reference and Importing .NET into Script Transformation
Importing CSV file with URL using DTS???
Dynamic SQL Server Destination???
Merge Replication Between two Existing Databases?
SSIS Package on X64 with Script Task
SELECT QUERY Without USING CASE
Simple Question: Testing an Update Script
Stored Procedure being saved in System Stored Procedures
concatenate a string within a loop from a temp table
Stored procedure ?

SQL Server

The target service name could not be found.
FTP Task - Delete remote files always fails
ODBC Returning success but actually failing (SQL Native)
Deployed reports have javascript errors?
temporary table not dropped after user disconnected (SQL2005)
Drillthrough action
Executing password protected packages
Some info on setting row delimiter values in package configurations
Making outbound HTTP requests from SQLCLR
Registry to store configuration values ?

Compilation/sec is more on production where recompilation / sec is zero

Hi Team,

Our production Environment is SQL server 2000 with SP3. I noticed lot of compilation/sec (where recompilation/sec is closed to ZERO). I know every stored procedure will get compiled initially then it may get recompiled for lot many reasons & I have very good understanding of reasons for recompilation & lot of document on that. Where as I am trying to understand what causes for compilation.

I noticed we are not using DBO prefix while calling the stored procedure & also recommended using sp_executesql instead of exec. Is there anything else I need to check

Is there any document on what causes for compilation other than creating the stored procedure. Once again I am not seeing recompilations.

Any help will be really appreciated.

Thanks

DJ Pallerla

Answer this question

Compilation/sec is more on production where recompilation / sec is zero

Answer this question