Defining views that cross multiple databases.

We have a few views that go across multiple database. Each database is its own submodel in ERStudio. However, when I try to define a view in one submodel, it can't see any of the tables in the other submodel/database. If I try to edit the view DDL to use multipart identifiers, the view becomes invalid even though it is a valid sql definition. 

Eg) CREATE VIEW v4.vwCrosswalk AS
SELECT
   codingScheme,
   eCodeKey
FROM Config WITH (NOLOCK)
   INNER JOIN [Exam]..ECode ECode WITH (NOLOCK) ON Config.configKey=ECode.configKey
WHERE Config.isDeleted IS NULL AND ECode.isDeleted IS NULL

Is there no way to support this kind of view that may start in one DB but reference a table in another DB?
Parents Reply Children
No Data