Very minor issue, linked server names aren't resolving in the SSMS code editor

• chuck.forbes

  SSCarpal Tunnel

  Points: 4294

  More actions

  May 19, 2017 at 4:32 pm

  #325915

  When writing T-SQL code, our Linked server names and objects aren't resolving (there's a squiggly line beneath them in the SSMS editor). Is that normal, or is there something we can do to make that work properly? When the procedure executes, there are no issues with privileges.

  I'm just not sure if there's something I'm missing, that will allow SQL Server to peek into this other instance and confirm an object's existence. We are forcing the Linked Server to use a specific account, when utilized.

  This is really nothing huge, but it would be helpful if it worked as I want it to, since it confirms that the appropriate privileges are in place when the target server is accessed.

  Thanks,
  --=Chuck

• caffeinated

  Ten Centuries

  Points: 1271

  More actions

  May 20, 2017 at 10:00 am

  #1943427

  Do you rely on SSMS native Intellisense for coding?

  I think this is normal.  SSMS makes a separate connection to pull metadata for Intellisense.  I don't think it's able to sense you're coding against a LinkedServer and then go probe the remote server for its database info.