thanks - i think you finally provided a clue to the maddening performance of intellisense. My issue is that the current TSQL script that i am debugging will not show up the latest changes during the subsequent step through. Even though sometimes it appears that the correct modified script is being run (as per local variables checks), the new changes will not show up in the screen (for instance, it executes on blank lines because there were lines inserted above, or the modified line still looks like the old line). Ohter times, there is no change and im executing the old script again.
refreshing the cache appears to work only inconsistently, and its a constant struggle to stop the debugging and try again to get my changes recognized.
So the clue you put out here is to be patient - that refreshing the cache is not immediate, or might take a bit of time. It will help me a lot if in fact that is the reason, and i guess i can cool my heels for a bit before re-executing my modified script.
My question is, is there any way to tell that its done? something that reports back on the status of the cache, or the refresh process? it sure would be helpful to know, so i will know to wait the 10 seconds, or 2 minutes, or 10 minutes, or whatever the number turns out to be.
thanks very much.