Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@olezhka tried that (although didn't try setting the checkpoint tbh, but tried various commands, including dropcleanbuffers... Nope, none of them clear the cache properly...
And yeah, mssql is in the tag so you assumed correctly :) -
@Bikonja ah ok, must have read the tag and forgot about that while typed the response :D #imagoldfish #findingdory
-
@olezhka I *really* know what that's like :D
There's a new kind of cache i didn't know about.
Just had to share this
Why SQL, why???
I have a proc I need to modify so I add a select into it. Drop the proc and recreate it, run it, new select not giving results.
Modify the select to inverse filter to see what I do have, recreate the proc, run it, still no results...
Run four different cache cleaning queries, still no results from the new select...
Add a "select 1" before the new select, recreate and run the proc and now I have the new 1 and also the other select now has results...
Change the filters back, still getting same results...
Remove the select 1, no results...
What kind of devil cache is this?
rant
mssql
cache