Intellisense is not working in Microsoft SQL Server 2014, it was working fine in Microsoft SQL Server 2012 but once I installed 2014 it is not working.
Under Tools -> Options -> Text Editor -> Transact-SQL -> IntelliSense it says it is enabled there.
I have also tried refeshing the IntelliSense cache with Ctrl-Shft-R but that doesn't work.
From my personal experience, SSMS IntelliSense is a pure crap, sometimes it works, sometimes it doesn't. I'd go for third party tools.
If you're willing to spend your cash, I'd recommend Redgate SQL Prompt.
If you need a free product, try dbForge SQL Complete, it's not as good as SQL Prompt, but does a decent job.
Perform following steps:
Under Edit -> IntelliSense -> Refresh Local Cache
Restart SSMS.Then try
After Refreshing local cache, if still not working, then try to delete temporary file of OS. for me it's work, I hope this will fix your's issue as well.
I am with SQL Server Management Studio 2014 and this working "Just hit Ctrl+Shift+R to force SSMS to refresh its cache." – Panagiotis Kanavos
Related
I am working on a project where I will be provisioned a SQL Server 2017 database server. However, the only version of SQL Server Management Studio available to me is 2008R2. I could request a newer version but this may take 1-2 months before it is finally installed on my machine.
Am I going to run into compatibility issues? Are there any database settings in SQL Server 2017 I would need to set in order to use this?
I am pretty unfamiliar with the MS suite of database tools so sorry for my ignorance in this! Thanks
In response to comments:
I have a managed system so I am not able to install or run software that has not been "approved". I have tried the portable version of VS Code but that did not work for me. I am going through the process of requests SSMS 2017 but like I said in the question this will not be available for 1-2 months. In the meantime will SSMS 2008 work?
As unlikely as this may be, I happen to have two, and only two, versions of SSMS installed on my machine; 2008R2 and 2017. I'm in the midst of an upgrade project.
I opened SSMS 2008R2 and was to connect to and generally poke around on a SQL Server 2017 server and the related databases. I didn't do anything too complicated (a few SELECT statments & an UPDATE), but they worked. The objects I expected to be visible were visible. And I didn't have to do anything to make it work. It just worked.
Mostly.
Except that every time I right clicked on a table, an error box opened with this message:
Index was outside the bounds of the array. (Microsoft.SqlServer.Smo)
But if I hit the OK button, the box cleared and the desired right click menu opened and functioned. That will get irritating, but if you poke around in the Options menu, there might be a way to make it stop. I invested no minutes trying to do that.
At the very least, you should be able to work while you're waiting for your upgrade.
For what it's worth, I work for a government contractor and have the same level of security constraints you do, so I feel your pain.
Another approach is to run sqlcmd, which would have been installed with SQL Server 2008R2. I was able to connect from sqlcmd to a SQL Server 2017 Docker container (external/internal ports 1433). I did not encounter any errors/warnings when creating a database and table, and running some light queries.
Interestingly, I was unable to connect to the same server using SSMS 2008R2. Perhaps the protocol used or the security required (e.g., TLS 1.2) for the underlying connection was different. Clearly it works based on Eric Brandt's results.
i would like to ask if anybody having the similar problems like me.
i have downloaded the newest SQL Server Management Studio 2016 Preview from Microsoft web site, and after i installed it (successfully and i need to restart my notebook said the warning box) then, suddenly nothing happens, there is a folder on the start menu that says SQL Server Management Studio 2016, but the folder is self is empty and i do not see the app, first i thought must be i missed something, so i went back and repair those SSMS (through the Repair Menu), but still it is giving me the same error, does anybody here have the similar problem and a way out of it?, since i need this SSMS 2016 to query to my Azure SQL Database.
Thanks!.
Roland
That happened with me few times when i tried to install it in not the Administrator mode.
So, try to do that in elevated mode, if that will not help, try to download it again or just rollback to the older version (2014), as it works perfectly with the SQL Azure. SSMS 2016 is still in preview, so the unexpected behavior may happen.
So, it turns out that in Windows 10, all the start menu options may not show up. Try visiting C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2016 RC3 in your File explorer to see if the SSMS shortcut is available there.
I installed SQL server 2012 and I have been using it with vs2012. For some reason, now that I have installed vs2013, if I go to "Create New SQL server database...", the option is grayed out.
Just to clarify:
I go to the server explorer tag -> right click data connections. In that list of options the "Create New SQL Server Database..." option is on the list but it is grayed out. Is it necessary for me to link vs2013 to it in some way? I may have done this as part of the original SQL server 2012 installation but I do not want to mess up that setup inadvertently.
Edit: It may (or may not) be worth mentioning that I can actually create Databases for vs2013 projects with vs2012. It is mainly a matter of it being awkward and just incorrect.
An out-of-date of VS2012 SQL Server Data Tools can cause conflict with built in tools for VS2013. Download the latest version of Microsoft SQL Server Data Tools.
The SQL Server 2008 R2 Management Studio intellisense stopped working a month ago though it is enabled. I read that this issue may be caused by the .NET framework 4.0 SP1 and tried some of the suggestions but nothing worked:
I have installed the cumulative update package: SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I re-registered the TextMgrP.dll
Any other suggestions what can be done?
The SSMS version is: Microsoft SQL Server Management Studio 10.50.1617.0
Make sure you are connected to SQL Server 2008 Edition. IntelliSense does not work with the previous versions of SQL Server.
IntelliSense should be enabled. There are two ways to verify whether IntelliSense is enabled or not. a) From Toolbar b) Go to Tools -> Options -> Text Editor -> Transact-SQL -> IntelliSense
IntelliSense should be refreshed with the latest changes in database. a) Press CTRL+SHIFT+R b) Go to Edit -> IntelliSense -> Refresh Local Cache
Go to Tools -> Options -> Text Editor -> Transact-SQL -> General -> IntelliSense Select Auto List Members and Check Parameter Information.
I got the same problem.
For me the only thing it works was to select the database manually from the source code.
I just add
use MYDATABASE;
GO
Im my case it looks like that the source code couldn't be associated to a default database.
I installed Developer edition of SQL Server 2008 R2 and find out intellisense is not working or show as other developer talking about.
Is there anything else I need to do to get intellisense working in SQL Server Management Studio?
What I do to get it to work?
Maybe you need to "refresh" the intellisense cache.
3) IntelliSense should be refreshed
with the latest changes in database.
a) Press CTRL+SHIFT+R b) Go to Edit >>
IntelliSense >> Refresh Local Cache
Full list of things to make sure of:
Connected to SQL Server 2008 edition
Intellisense enabled
Intellisense refreshed
Correct settings for "Statement completion"
Check here for a complete instructions with screenshots.
If you have recently installed Visual Studio 2010 SP1 you may be encountering a bug. Microsoft has confirmed that VS 2010 SP1 effectively breaks intellisense in SQL Management Studio.
Here are a couple of options you can try:
DevArt's SQL Complete -$0 free
RedGate's SQL Prompt - $195 <-You can find it at red-gate.com.
First and foremost you must be working with a SQL Server 2008+ instance, for the server to be able to give you the metadata for intellisense.
It is a fine art making intellisense work for you.
The first thing you can to do make it recognize the database context is to put
USE databasename;
at the top of your query window. This gives it a better grasp of where you are working.
The next thing you need to get used to is to write your queries in a different order, fill in the FROM clause first, so the skeleton should be something like
SELECT ^
FROM tblname
or
UPDATE tblname
SET ^
At the position marked ^, intellisense will have a good idea of what db/table context you are working in.
UPDATE a
SET a.^
FROM tblname a, tbl2 b
Without fully specifying the join condition, just listing the tables as above allows intellisense to work with a.
There are many other tricks, such as if you renamed objects, you're best off to start a new query window or disconnect from the server completely and reconnect, or even restarts SSM Studio.
Other reading:
http://www.techrepublic.com/blog/datacenter/using-intellisense-in-sql-server-2008/446
http://blog.sqlauthority.com/2009/03/31/sql-server-2008-intellisense-does-not-work-enable-intellisense/
You also need to be talking to at least a 2008 server.