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

> Are you also seeing SP:ExecContextHit or SP:CacheInsert right after the
> SP:CacheMiss? If so, one possibility is that your stored proc is called
> sp_Something but is in a user database. In that case, since the name beings
> with sp_, MSSQL looks first in the master database but doesn't find the proc
> (SP:CacheMiss), then it tries the user database and finds the proc
> (SP:ExecContextHit). If that isn't the case, then perhaps you can give more
> information about what the proc is doing, which database it's in, exactly
> which SP events you see when you execute the procedure, and in what order?
>
> Regarding memory, have a look at "Monitoring Memory Usage" in Books Online,
> as well as this page:
>
> http://www.sql-server-performance.co...ers_memory.asp
>
> Simon