November 10, 2011 at 3:52 am
Scott Levy (11/9/2011)
Just a last update on this if anyone is interested as I think I may have found the source of the inconsistency.I believe that it was the local intellisense cache of the DB schema that management studio holds. I have been having issues with it flagging tables and fields as invalid when they are definitely there, a force refresh of the local cache and the issue goes away.
Scott
problem of cache that occurs with intellisense, not affect the results of server!!!
November 10, 2011 at 3:53 am
codebyo (11/10/2011)
Dev @ +91 973 913 6683 (11/9/2011)
I am not convinced. Intellisense helps developers to write SQL code in SSMS with ease. It’s IDE feature. It should not affect your query results.I was able to reproduce the behaviour where intellisense would be outdated and sometimes would show syntax errors while editing the code.
But it would execute the commands with no erros as that issue doesn't affect the SQL parser. I can't see how a intellisense bug could influentiate the parser's behaviour.
Best regards,
I agree with you!!!!:-D
November 10, 2011 at 3:54 am
Dev @ +91 973 913 6683 (11/9/2011)
Scott Levy (11/9/2011)
Just a last update on this if anyone is interested as I think I may have found the source of the inconsistency.I believe that it was the local intellisense cache of the DB schema that management studio holds. I have been having issues with it flagging tables and fields as invalid when they are definitely there, a force refresh of the local cache and the issue goes away.
Scott
I am not convinced. Intellisense helps developers to write SQL code in SSMS with ease. It’s IDE feature. It should not affect your query results.
I agree with you!!!
November 10, 2011 at 5:07 am
Scott Levy (11/9/2011)
Just a last update on this if anyone is interested as I think I may have found the source of the inconsistency.I believe that it was the local intellisense cache of the DB schema that management studio holds. I have been having issues with it flagging tables and fields as invalid when they are definitely there, a force refresh of the local cache and the issue goes away.
Scott
Interesting notion and even more interesting solution... I've seen stranger things happen but not by much. We had similar problems with Intellisense redflagging tables and columns. It hasn't affected any runs (yet) but I can see it coming someday. How did you refresh the local cache, Scott?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 10, 2011 at 2:41 pm
How did you refresh the local cache, Scott?
Edit | Intellisense | Refresh Local Cache (Shift+Control+R)
It only appears when you have a query open for editing I think.
Scott
November 10, 2011 at 3:22 pm
Scott Levy (11/10/2011)
How did you refresh the local cache, Scott?
Edit | Intellisense | Refresh Local Cache (Shift+Control+R)
It only appears when you have a query open for editing I think.
Scott
Just to be clear... You did not receive any errors upon execution. You were just stumped as to why it was underlined in red as a non-existent column?
Jared
Jared
CE - Microsoft
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply