Microsoft SQL Server 2008 R2 810-08230 User Manual

Product codes
810-08230
Page of 236
 
Data Stewardship 
CHAPTER 7
 
129
  Integration Management
  Use this area to create and process batches for im-
porting data from staging tables into the MDS database, view errors arising from 
the import process, and create subscription views for consumption of master data by 
operational and analytic applications .
  System Administration
  Use this area to create a new model and its entities and 
attributes, define business rules, configure notifications for failed data validation, and 
deploy a model to another system .
  User And Group Permissions
  Use this area to configure security for users and 
groups to access functional areas in Master Data Manager, to perform specific func-
tions, and to restrict or deny access to specific model objects. 
Data Stewardship
Master Data Manager is the data stewardship portal in which authorized business users can 
perform all activities related to master data management . At minimum, a user can use this 
Web application to review the data in a master data model . Users with higher permissions can 
make changes to the master data and its structure, define business rules, review changes to 
master data, and reverse changes .
Model Objects
Most activities in MDS revolve around models and the objects they contain . A model is a 
container for all objects that define the structure of the master data. A model contains at least 
one entity, which is analogous to a table in a relational database . An entity contains members
which are like the rows in a table, as shown in Figure 7-1 . Members (also known as leaf mem-
bers) are the master data that you are managing in MDS . Each leaf member of the entity has 
multiple attributes, which correspond to table columns in the analogy .
Attributes
Members
FIGURE 7-1 
The Product entity 
By default, an entity has Name and Code attributes, as shown in Figure 7-1 . These two at-
tributes are required by MDS . The Code attribute values must be unique, in the same way that 
a primary key column in a table requires unique values . You can add any number of addi-
tional free-form attributes to accept any type of data that the user enters; the Name attribute 
of the Product entity shown in Figure 7-1 is one such attribute .