It's interesting to see that NS seems to do some c...
# suiteql
w
It's interesting to see that NS seems to do some cacheing of the exact same query for a while. If I execute the code for the same subs again, it falls down to 1,3s for each. But changing anything in the query will make it slow again. I wonder for how long it keeps the cache? Is it a optimized version of the query that is cached or is it the actual result? What happens if the result changes? netsuiteemployee = black square 📦
m
How long the cache of the execution plans persists is a setting on the sql server, at least in ms 😉 Very good analyzis, I hope ns can use this to optimize some of their performance issues.
In this scenario it would as I see it help to index the subsidiary column which already should be a part of the key, but who knows 🤷‍♂️