As long as you have AutoUpdate statistics turned on (which is the default)
this will happen automatically at the proper times. SQL Server keeps track
of the number of changes in each table and will update the statistics at a
point that is determined via an internal algorithm. When this happens any
sp's accessing that table will get recompiled the next time they are run.
You can manually force the update of statistics via sp_updatestats or UPDATE
STATISTICS if you feel the need. But you should first determine for sure
that the automatic way is not adequate before doing so, otherwise you should
leave it as is.
Andrew J. Kelly
SQL Server MVP
"Bhupesh Saini" <bsainibenefitconcepts.com> wrote in message
news:008901c343ee$6a4ec350$a501280aphx.gbl...> I have read somewhere before that if the data in the table
> changes due to inserts and updates, it is beneficial to
> recompile the stored procedures accessing those tables.
> this would help a a new query plan being generated for the
> stored procedures and help in perfomance.
> However, I would like to know when would be a good time
> for the stored procedures to be rebuilt. How do I
> determine that the data has changed and it would be
> benfeficial for the stored procedure to be recompiled. Do
> I need to guess based on system usage and come up with my
> own optimum schedule (monthly, weekly etc.) for the
> recompile of the stored procedures.
> Bhupesh Saini