September 8, 2011 at 12:29 pm
I recently imported a table from an Excel spreadsheet and I am writing a simple select stored procedure against it. For some reason there is no intellisense during the design of the sp. Is it possible the stored procedure or the table that it is pulling data from has a corruption issue. I was able to recreate the sp from scratch, giving it a different name, and it has intellisense. I have only noticed this behaviour on this one particular sp and have never seen this kind of issue before. I'm hoping it is just a glitch but wanted to throw it out there in case there is something more I need to be aware of.
September 8, 2011 at 12:38 pm
Try closing out of your SSMS and going back in. That usually does it for me as I believe the data needs to be loaded into cache.
Thanks,
Jared
Jared
CE - Microsoft
September 8, 2011 at 12:50 pm
No need to close SSMS. You just need to refresh the local intellisense cache. ctrl - shift - R or use the menu Edit -> Intellisense -> Refresh Local Cache. 🙂
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
September 8, 2011 at 12:50 pm
I did try that. I even tried using the SSMS on the SQL Server itself and had the same issue. I had thought maybe it was my machine.
September 8, 2011 at 12:51 pm
Edit-> Intellisense -> Refresh Local Cache (Ctrl-Shift-R)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 8, 2011 at 12:54 pm
Other issues I have seen is if I am accessing a 2005 database or with the compatibility level of the database being 90. That could be throwing it off as well. Check the compatibility level of the database you are accessing, it should be 100.
Thanks,
Jared
Jared
CE - Microsoft
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply