When looking to make a cross database query, there are a few options। The most basic method s the fully qualify your table access with the name of the table। In this case, I could access the Subscriber table from the Orders database as follows:
select * from Subscription.dbo.subscriber
I didn't choose this technique, mainly because of the linked server issue. If I were to move this database to it's own server, which could happen if either of these databases or the load on the server grew, then any process that accessed this table would require recording. Not that I'm against the work, but it's easy to miss a function or stored procedure somehow when moving databases. I much prefer to centralize my code changes as much as it makes sense.
For that reason, I chose another method of accessing the table. I created a view, which I could have called subscriber so the access is transparent. However since I like to be aware of when I'm accessing a view, I named it as follows:create view vSubscriber
as
select first
, last
, startdate
, enddate
, subscriberid
, email
from subscription.dbo.subscriber
In this way I can develop all code in the Orders database just as if the subscriber or any other table were local. If I move the subscriber database (more likely) or rename it (unlikely), then I only have to change the code in one place: the view.