Overview of Data Synchronization

From TeamServer ER/Studio
Jump to: navigation, search

Go Up to Administrator Guide

ER/Studio Team Server provides features on top of data from ER/Studio Repository, which can store data from ER/Studio Business Architect and ER/Studio Data Architect.

However, the data you see in ER/Studio Team Server does not come directly from ER/Studio Repository. Instead, ER/Studio Team Server has a repository of its own, the Reporting Repository, which holds a copy of the data from ER/Studio Repository. As data changes in ER/Studio Repository (ER objects, users and roles are added, deleted or updated), you must update ER/Studio Team Server to keep both repositories in sync.

For example, when a user is assigned to a role in ER/Studio Business Architect or ER/Studio Data Architect, the new permissions of the user are not available to that user when he logs in to ER/Studio Team Server, until you run a synchronization process. Similarly, a new user added to ER/Studio Team Server does not have access to any ER object of the Reporting Repository until you synchronize ER/Studio Team Server with ER/Studio Repository.

You can synchronize the data shared between the ER/Studio Repository database and the ER/Studio Team Server Reporting Repository database on demand or in a schedule, and you can perform the synchronization continuously or periodically.

You should start by configuring which content you want to synchronize, and then proceed to synchronize it. See in ER/Studio Repository Data that ER/Studio Team Server Supports which data you can synchronize with ER/Studio Team Server.

Notepad blue icon 2.pngNote: Files saved in later versions of ER Studio Data Architect may not work with ER/Studio Team Server if they use new features. For example, if you use SQL Server 2014 for your Physical Model in ER Studio DA 9.7, you will need to update to the corresponding version of ER/Studio Team Server for those files to synchronize.


See Also

Personal tools
Product Family Wiki
Product Videos