Reusable asset service database setup

[ck663]

Hi,

I have two models, both hosted in separate DBMS databases. I want to be able to share packages between the two models in both directions. Do I need a third DMBS database to configure as the registry for RAS, or can each of the existing databases act as a registry for the packages of the other?

Cheers

[Uffe]

Hello,


RAS needs its own database.

Strictly speaking that might not be true. A RAS project has the same database schema as a regular project, so it might be possible for a project which holds RAS registries (one RAS instance contains X registries contain Y assets) to also hold regular packages, elements and diagrams, but it's not something I've ever tried and it's not what's indicated by the documentation.

But unless you want to experiment, assume RAS has to be set up separately.

That said, if all you want to do is to move versions of models between two projects, you can use baselines.
With baselines you can work in project A and import baselines from project B and vice versa.

RAS is better as a version management system, in part precisely because it is separate from the "working" projects (less risk of accidental deletion for one, and dependency management for another), but for a small setup cross-project baselines can work reasonably well.


/Uffe

[ck663]

Thanks for the detailed reply!