Contents
How to create SSDT project with working linked server references?
The other one, that is supposed to work as an “Controller” instance, is basically supposed to run different stored procedures on the “worker” database on the 10 production servers. So to realize this, I have scripted 10 Linked Server objects within the “controller” and call the different SPs in the “worker” databases.
When do I get broken references in SSDT?
Within the SSDT project / solution, I get broken references whenever I use the Linked server objects. Sure, the schema is not aware of the linked server names, since they are only in a string constant in the above script. Sample: (I translated the message on my own, no guarantee it’s exactly right)
What’s the difference between an error and a warning in SSDT?
According to the message shown in the Question, this is actually a warning (“warnung”) and not an error. An error will stop the build process and prevent the project from being published to the server. Warnings merely show up in the “Error List” window, but don’t prevent the build or publish processes from completing.
How many production servers are there in SSDT?
One of them, let’s call it the “worker” is supposed to get deployed to about 10 different production servers. The other one, that is supposed to work as an “Controller” instance, is basically supposed to run different stored procedures on the “worker” database on the 10 production servers.
Can a linked server be created on a SQL Server?
Here is a sample for the Linked Server scripts: So far so good, this works and the Linked Servers are created on the controller SQL Server and I can use them. Within the SSDT project / solution, I get broken references whenever I use the Linked server objects.
Why is MY SQL Server not using SSDT?
(A) isn’t deployed – the external tool is also installed and configured to produce the same database. Strangely, I was later able to alter views in (B) and publish, but then wanted to remove a column.