In SSMS (versions 17 and 18), IntelliSense is not working with the sa user, but it is working with another user. If I connect to a SQL database with the sa user and create a query window, IntelliSense does not work in this window. However, if I make a second connection to the same database with another user and create a query window, IntelliSense works. If change back to the query window with sa user, IntelliSense again does not work.

I have an SQL Server 2016 database. This database is hosted on a **shared** server, and is managed by a central DBA team. In an effort to harden data security on the Production server, the DBA team has taken the approach to revoke/disable all public roles (i.e. DENY everything to the public role). I believe this was done to limit (meta)data access to *other* databases on the same server, presumably along these lines: https://dba.stackexchange.com/questions/220225/is-it-best-practice-to-revoke-server-permissions-to-the-server-public-role-on The problem is that this setup prevents IntelliSense from working on Microsoft SQL Server Management Studio. I think it's the situation Aaron Bertrand cautions on here: https://dba.stackexchange.com/a/116814/180921 I have elevated access rights (RWED) to my database, but am not a full admin (this role is restricted to members of the DBA Production team). **Is there a possible solution here? How can IntelliSense be made to work on my database, while respecting DBA desire to limit metadata view for *other* databases**

Okay. So I'm breaking some new ground and trying to get into Azure Data Studio. I'm having a problem with intellisense that seems to be a bug with Azure Data Studio but I'm not sure. I have issues with basic queries. Foreign keys, select statements and insert statements are all telling me in this example that chocolate_category does not exist, it says it is an invalid object name, or that the foreign key is invalid because the table name is invalid, etcetera. Simply put ADS is erroring on tables that do in fact exist. In this case, I was able to insert data even though the intellisense thinks the table name is invalid. Then I was able to select from the table. Why is this happening and how can I fix this? Control-Shift-R does not work to refresh intellisense. Adding dbo. prefix to the table name does not work either. As you can clearly see in this image, the table exists within the database that I'm located. The query shows an error, however running it puts up a result. If my code works on the table name, then why the error? I have found that it is possible to continue through this error, but it is very annoying to me to be told something is broken that is not broken.

I would like to navigate to open a directory path from an in-line commented UNC path. SSMS integrates with Windows Explorer and Explorer allows UNC navigation from the address bar. Indeed, when in the integrated browser, it is possible to navigate among UNC paths. HOWEVER, the click-thru functionality provided for http:/ prefaced URLs in the text editor of SSMS does not seem to exist for UNC paths. The Web Browser section of Options / Environment appears to open Internet Explorer options and the Text Editor / Plain Text / General section has the "Enable single-click URL navigation option", but does not appear to allow definition of what is detected as a URL. Screenshots linked below (added sample code below) use [master] go -- http://www.google.com -- \\servername\unc\BackupFolder\ select 'This query needs to be uploaded to the URL' Header union select 'and also saved for archiving at the UNC path' union select 'so is it possible to clickthrough to both?'

I have installed SQL server 2016 whose details are as in below screenshot: My queries are pointing to Azure SQL DB. Below are the screenshot of some other settings that I have found over the internet and applied: I have also tried by refreshing the local cache and reconnecting to the database. Please share your expert opinion here and help me to make this work.

My sql server management studio intellisense is not working, below is my SSMS version and screen shot that I have tried, my SQL server is not installed locally but I am accessing the sql server remotely, maybe a firewall issue? It works at will, sometimes work sometimes does not work I have this blue icon on my database instance, it might be blocking it as it is some firewall issue

Do you know any way to force intellisence in Azure Data Studio to find tables in custom schemas? As you can see I have tables: - dbo.TableC - schemaA.TableB When typing a query, only TableC is found by intellisence. I know that full SQL Server Management Studio does not do this by default as well but there are some extensions that do this (e.q. SqlComplete). Is there anything for Azure Data Studio with similar functionalities? **Update:** I created an issue on Azure Data Studio github. It's here: https://github.com/microsoft/azuredatastudio/issues/18514

In SSMS, are IntelliSense and SQLCMD mode mutually exclusive? Is there any way to make IntelliSense work when SQLCMD mode is enabled? (I use SQLCMD a lot) I'm trying to understand why IntelliSense becomes disabled in SQLCMD mode, but there's so much information for both of them in Google search results that I can't find an obvious answer. I found this good discussion about it, but not really an answer to my question.

I'm running SSMS 2019 on my laptop, connecting to 2 different SQL Servers - 2008 R2 and a SQL 2016 machine. When I'm physically in the building where the servers reside, Intellisense works great. But on days when I'm working from home, connected through VPN, Intellisense is very spotty. Usually it completely fails to work at all, but every once in a while, it'll auto-fill a database name as I type, but never a table or field name. I've tried refreshing the local cache (CTRL+Shif+R), but that hasn't helped. Any ideas? As requested below, here are the results of running Test-NetConnection "Emden" -port 1433 over VPN connecion:

PS C:\Users\cjm> Test-NetConnection "Emden" -port 1433


ComputerName     : Emden

RemoteAddress    : 192.168.10.56

RemotePort       : 1433

InterfaceAlias   : Ethernet 2

SourceAddress    : 192.168.11.46

TcpTestSucceeded : True

This problem is really proving to be a tricky one (and quite annoying). In SQL Server Management Studio 2008, up until a few days ago my IntelliSense was working great. Then all of a sudden it stopped. The icon as it as enabled on the toolbar menu, and under Tools -> Options -> Text Editor -> T-SQL -> IntelliSense it says it is enabled there. I have tried refeshing the IntelliSense cache with Ctrl-Shft-R but that doesn't work either. Any ideas what happened to my IntelliSense and what I need to do to get it back?

I have created two stored procedures that I want to be available from all databases on SQL Server 2017. I created them in the master database, used sp_ as the prefix for both of them (e.g. sp_MyProc1 and sp_MyProc2), and then ran sp_ms_marksystemobject on them to make them system objects. I can indeed call them from any database and they work as expected. The problem is that Intellisense doesn't know that they're there unless master is the default. It does recognize built in system procedures like sp_HELP. Is there another setting I need to change to make Intellisense recognize them? We're using SSMS v17.9. I tried putting them in the sys schema, but apparently SQL Server doesn't allow that on master. Thank You, Robbie

I'm using SSMS 17.6 which is the latest version at the time of posting. It is supposed to have the latest official IntelliSense version. However, it underlines my scripts with red squiggles where I'm using temp tables, linked server tables and synonyms. It's difficult to edit queries because I don't get correct error detection. Everything is filled with "errors", but queries run, and the results are what I want, as expected. I've tried a few third-party addons like SQL Complete and SSMSBoost, but they don't seem to improve IntelliSense, but rather extend the SSMS in other ways like tooltips and popups. Or maybe I just haven't figured out how to use them for improving IntelliSense. What can I do to make IntelliSense correctly handle these things? If there is no first-party way, then what third-party extensions exist and how to configure them to improve error highlighting?

I have created an Active Directory Group and created it as a user, we'll call it "AD SQL", in my DB. I can successfully login in using Active Directory Authentication and read/write. However, Intellisense is not working for any Active Directory users. If I log in using my Active Directory Admin, "AD ADMIN", Intellisense works fine. Can anyone tell me what permissions/roles/view/etc are needed for a user to have access to Intellisense? My "AD SQL" user the following roles/permissions: - db_owner - db_datareader - db_datawriter - GRANT CONNECT (DATABASE) - GRANT VIEW DEFINITION (DATABASE) And I have already tried Refreshing Cache/Restarting SSMS.

I am using SSMS 2016 (ver: 13.0.15000.23) and connecting to SQL Server database 2016 (ver: 13.0.5081.1). IntelliSense is not working on my SSMS. I tried the following: * Tools >> Options >> Text Editor >> Transact-SQL >> IntelliSense, and select Enable IntelliSense * Tools >> Options >> Text Editor >> Transact-SQL >> General, and verify Auto list members and Parameter information check boxes are checked * Query >> IntelliSense Enabled * Verify that SQLCMD is disabled * Refreshed IntelliSense cache (Ctrl+Shift+R) * Making sure no compile errors are in the query * Uninstall and reinstall SSMS I asked other members in my team and IntelliSense only works sporadically for them, if it does. **Question:** Is there a server setting which is disabling IntelliSense on SSMS? --- I've already gone through all of these questions: * https://dba.stackexchange.com/q/6145/32970 * IntelliSense is not working at SQL Server Management Studio * Why is SQL Server 2008 Management Studio Intellisense not working? * SQL Server Intellisense not working on *some* servers * SQL Server 2008 R2 intellisense doesn't work * https://dba.stackexchange.com/q/90475/32970 I have limited permissions on the instance, but I can select and update records in the database I'm working in (I didn't try insert). I can see around 1,600 names of objects and columns by running: SELECT o.name, c.name FROM sys.objects o INNER JOIN sys.columns c ON o.object_id = c.object_id WHERE o.is_ms_shipped = 0;

A newly created table or procedure will always have the red squiggly underline until the SQL Server Management Studio is restarted. Is there a way to get rid of it without re-start the SSMS? Or it's a feature that SSMS needs to update? Thanks!

I can connect to multiple database servers. Intellisense works on all of the connections except one. It used to work on this connection also until recently. I did the following: - Enable Intellisense (on the toolbar and edit > intellisense) - Disable and then enable intellisense - Install SP3 - Reboot SQL (and PC)

I am not sure if this is possible, but when writing a query to select from a table, when I bring up the intellisense drop down with CTRL + Spacebar, it gives me a list of all variables (global, and on the table). Is there any way to make this only show the variables in the table I am selecting from? Its basically completely useless unless you know the name of the field already, so then what is the point of the intellisense drop down?

I have SSMS 2014 installed on my desktop, and many 2012 and 2014 databases running in our data center. So far I found one database (database A) doesn't have IntelliSense working, for exampletyping: SELECT [put cursor here] FROM sys.objects and moving cursor between select and from, pressing CTRL + J, I can see popup options for other databases, just not for database A. I have checked all options and refresh local cache, all don't work, and I am using an account which has *sysadmin* permission. * The compatibility level is 11.0 * Version is >Microsoft SQL Server 2012 - 11.0.5556.0 (X64) Oct 31 2014 16:50:24 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) I can log on to the db server which is in US and see IntelliSense working there, it just doesn't on my desktop (in Australia). Is it most likely a latency issue? is there a timeout limit or setting for this feature?

Our remote SQL Server was recently upgraded to 2014. I installed SQL Server Management Studio 2014 on my Windows 10 client computer. At first, everything seemed to be going great, until I noticed that IntelliSense is intermittent. By "intermittent" I mean that on the same computer, while working on the same script, IntelliSense might appear some times and not appear at other times. Before the upgrade to 2014, this never happened. Now it happens all the time. Here's a specific example. Suppose I'm typing SELECT DISTINCT * from dbo. The moment I type the period, I expect IntelliSense to list the available tables, as it always does. So by intermittent I mean that sometimes I see the list of tables, and sometimes I don't. This just a specific example of how the symptom manifests. This is not restrictive to table names. I mean that whenever I expect Intellisense to appear, it doesn't always appear. I checked the obvious: Troubleshooting IntelliSense (SQL Server Management Studio) reconfirmed what I already knew and didn't help. I've tried these things. - Closing the remote database connection and reconnecting - Refreshing the IntelliSense cache, both by Ctrl-R and through the menu Edit > IntelliSense > Refresh Local Cache - Making sure all Windows Updates were applied - Checking server connectivity with Ping (average 9 milliseconds) This is not a duplicate because while other forum posts list the above steps as "answers" they are not answers for me. They do not solve the problem of intermittent IntelliSense. Is there anything else i can do to fix this problem?

I have literally installed on my development machine three different versions of SSMS standalone: 2008, 2012, 2014, and I work with SQL Server 2008 databases. On every single one of those versions, I tried to have IntelliSense display my available columns when I type a table alias and a dot "Table." for example. But that doesn't show up over 90% of the time. This happens similarly on any SSMS version I try. I've searched for other people having this issue and found various cases, but none of those provided solutions, such as refreshing the IntelliSense cache and disabling/re-enabling IntelliSense itself, de-selecting e re-selecting certain options, work for me. Could this be a problem related to the instances of SQL Server that I am connecting to, rather than with SSMS itself? Edit: I have also tried to install a third party addon to SSMS, it then starts displaying as expected, but cripples my performance (making typing somewhat slower as it loads things in the background, which I really don't like), so I would rather fix the original functionality instead of resorting to that. Thanks