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