March 11, 2005 at 3:41 pm
Its a surprise to read that!
So if, purely hypothetically, you had not that long ago gone through your entire applications 800 stored procs, ammended them all to be dbo.procname and changed every exec to include dbo. prefix and every call from asp to the same stored procs because you'd discovered it was good practice to guarantee cache hits...
You might have WASTED YOUR TIME because if there was a different case in any SP name or parameter name (*very likely*) when called from asp or another SP you would still not get as cache hit.
This is absolutely STUPID to enforce case for a cache hit and would only make sense if case was enforced when defining and calling the SPs themselves; t-sql and asp etc are all case insensitive - argh profanities!!
In my view this is definitely a flaw, a bug even.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply