esteban_calle@hotmail.com (J?r?my) wrote in message news:<6e7e2caf.0311120247.674d4cad@posting.google. com>...
> Hi Simon,
>
> Thanks for your comments.
>
> So, what I have in the Profiler:
>
> RPC:Starting --> EXEC dbname.dbo.Myproc @Param
> SP:CacheMiss --> Myproc
> SP:ExecContextHit -->
> SP:Starting --> EXEC dbname.dbo.Myproc @Param
> ...
>
> The stored procedure that have the same profiling don't begin with
> sp_*
> but with Misc_* and return a recordset.
>
> Regarding Monitoring memory, I have already checked it, before sending
> a messsage to this group, and I didn't find any problem.
> The server has 7Gb with 6Gb set to SQLServer (with AWE)
> The SQL cache Memory is about 12Mb.
>
> Then I don't know what happened.
>
> Best,
> Jeremy
>

<snip>

In that case, another possibility is that you are not calling the proc
with exactly the same name, ie. you have changed the case of the
procedure name:

create proc dbo.p
as
select 1
go

exec dbo.p -- SP:CacheInsert
exec dbo.p -- SP:ExecContextHit
exec dbo.P -- SP:CacheMiss, then SP:ExecContextHit

Changing the case of the database name or owner doesn't result in a
cache miss, but changing the case of the procedure name does.

Simon