Hi everyone,
it seems to be something really simple, but I'm hitting the wall here.
Where does sql 2005 actually keep stored procedures code?
The issue is:
When I change the code of SP from SQL Management Studio it works fine.
I can modify code without any problems. But when I connect to sql server
from
asp page the code is still unchanged. It looks like SQL server cached the
old one.
Could you point me to a right direction please?

Thanks.

Make sure you don't have multiple copies of the same procedure under
different ownernames ...

(ie-- select uid, name from sysobjects where name = 'myprocname_sp')

If that returns multiple records it might be you're modifying one while
calling another (differentiated only by owner) from your asp page.

Checked this.
Not a case. Only one copy of SP is in a database.

Any other thoughts?
Thanks.

[quoted text, click to view]

[quoted text, click to view]
database you think it is? ODBC (assuming you're using this) properties
haven't change or anything like that? I've just never heard of sp
caching or resultset caching that persisted over multiple days.

Syscomments, however I suspect you're asking the wrong question.

The question you should be asking, I suspect is how can you have two
different sprocs with the same name.

Another possibility is that the connection string's pointing to a
different database. Several times have I connected through Sql
management, and compile a sproc into master, then scripted it, added a
use clause etc,