It's nothing special. It would simply be a linked server that you add to your environment that will always have the same name.
An example of this is that we have a need to read from DB2 computers from our SQL Servers. Originally, they were AS400 boxes and were later upgraded to PowerSystems boxes with computer names, IP address, logins and passwords. We didn't need to change a lick of code in our Dev/Staging/UAT, or Prod boxes. We had religiously used synonyms to point to the Linked Server and the names of the Linked Servers were exactly the same in all 3 environments. All we did was drop the existing linked servers, stand up 3 new ones with exactly the same name as the originals and we were done.
This same methodology keeps us from having to make code changes when we promote code from Dev to Staging/UAT, and Prod. Of course, we don't need to change the linked servers for that because they're all named the same.
You can do similar on a single SQL Server. Instead of having synonyms the refer to objects using the 4 part naming convention, you can have a "loop back" Linked Server that points to a database on the same server instance. If that database ever has to move to another machine, all you need to do is drop and recreate the Linked Server with the same name but pointing to a different server.
So, "Particular Name" is whatever you want it to be for the "particular case" you're using it for and keep that same name no matter what happens or where you move things.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems