Content deleted Content added
rmv non-WP:RS; req cite |
Cander0000 (talk | contribs) Undid revision 1279259633 by 2605:59C8:10:A610:B538:7556:9E5A:2F25 (talk) Some of the personnel details are a bit too 'in the weeds'; The Silverlight-to-pure HTML note is already addressed in the overview section |
||
| (21 intermediate revisions by 14 users not shown) | |||
Line 1:
'''Microsoft SQL Server Master Data Services''' (MDS) is a [[Master Data Management]] (MDM) product from [[Microsoft]] that ships as a part of the [[Microsoft SQL Server]] relational database management system.<ref>{{cite web | url=https://msdn.microsoft.com/en-us/library/ms130214.aspx | title=SQL Server technical documentation - SQL Server }}</ref> Master data management (MDM) allows an organization to discover and define non-transactional lists of data, and compile maintainable, reliable master lists. Master Data Services first shipped with Microsoft SQL Server 2008 R2. Microsoft SQL Server 2016 introduced enhancements to Master Data Services, such as improved performance and security, and the ability to clear transaction logs, create custom indexes, share entity data between different models, and support for many-to-many relationships.
==Overview==
In Master Data Services, the model is the highest level container in the structure of your master data. You create a model to manage groups of similar data. A model contains one or more entities, and entities contain members that are the data records. An entity is similar to a table.
Like other MDM products, Master Data Services aims to create a centralized data source and keep it synchronized, and thus reduce redundancies, across the applications which process the data.<ref name="roadmap"/>▼
▲Like other MDM products, Master Data Services aims to create a centralized data source and keep it synchronized, and thus reduce redundancies, across the applications which process the data.
Sharing the architectural core with Stratature +EDM, Master Data Services uses a [[Microsoft SQL Server]] database as the physical data store. It is a part of the ''Master Data Hub'', which uses the database to store and manage data [[Entity Data Model|entities]].
Master Data Services allows the master data to be categorized by hierarchical relationships, such as employee data are a subtype of organization data. Hierarchies are generated by relating data attributes. Data can be automatically categorized using rules, and the categories are introspected programmatically. Master Data Services can also expose the data as [[Microsoft SQL Server]] [[view (database)|views]], which can be pulled by any [[SQL]]-compatible client. It uses a role-based access control system to restrict access to the data. The views are generated dynamically, so they contain the latest data entities in the master hub. It can also push out the data by writing to some external journals. Master Data Services also includes a web-based UI for viewing and managing the data. It uses [[
▲Sharing the architectural core with Stratature +EDM, Master Data Services uses a [[Microsoft SQL Server]] database as the physical data store. It is a part of the ''Master Data Hub'', which uses the database to store and manage data [[Entity Data Model|entities]].<ref name="roadmap"/> It is a database with the software to validate and manage the data, and keep it synchronized with the systems that use the data.<ref name="arch">{{cite web | url = http://msdn2.microsoft.com/en-us/library/bb410798.aspx | title = Master Data Management (MDM) Hub Architecture | author = Roger Walter | publisher = MSDN TechNet | accessdate = 2007-09-25}}</ref> The master data hub has to extract the data from the source system, validate, sanitize and shape the data, remove duplicates, and update the hub repositories, as well as synchronize the external sources.<ref name="arch"/> The entity schemas, attributes, data hierarchies, validation rules and access control information are specified as [[metadata]] to the Master Data Services runtime. Master Data Services does not impose any limitation on the data model. Master Data Services also allows custom ''Business rules'', used for validating and sanitizing the data entering the data hub, to be defined, which is then run against the data matching the specified criteria. All changes made to the data are validated against the rules, and a log of the transaction is stored persistently. Violations are logged separately, and optionally the owner is notified, automatically. All the data entities can be [[Revision control system|versioned]].<ref name="roadmap"/>
Master Data Services
▲Master Data Services allows the master data to be categorized by hierarchical relationships, such as employee data are a subtype of organization data. Hierarchies are generated by relating data attributes. Data can be automatically categorized using rules, and the categories are introspected programmatically. Master Data Services can also expose the data as [[Microsoft SQL Server]] [[view (database)|views]], which can be pulled by any [[SQL]]-compatible client. It uses a role-based access control system to restrict access to the data. The views are generated dynamically, so they contain the latest data entities in the master hub. It can also push out the data by writing to some external journals. Master Data Services also includes a web-based UI for viewing and managing the data. It uses [[AJAX]] in the front-end and [[ASP.NET]] in the back-end.<ref name="roadmap"/>
SQL Server 2016 introduced a significant performance increase in Master Data Services over previous versions.<ref>{{Cite web|url=http://www.faceofit.com/why-is-sql-server-2016-is-faster-than-ever|title=Why is SQL Server 2016 is Faster Than Ever|date=11 March 2016}}</ref>
▲Master Data Services also includes certain features not available in the Stratature +EDM product. It gains an [[Web service]] interface to expose the data, as well as an [[API]], which internally uses the exposed web services, exposing the feature set, programmatically, to access and manipulate the data. It also integrates with [[Active Directory]] for authentication purposes. Unlike +EDM, Master Data Services supports [[Unicode]] characters, as well as support multilingual user interfaces.<ref name="roadmap"/>
== Terminology ==
Line 23 ⟶ 22:
Other attributes however, will be of type 'free-form' (most common) or 'file'.
* ''Attribute Groups'' are explicitly defined collections of particular attributes. Say you have an entity "customer" that has 50 attributes — too much information for many of your users. Attribute groups enable the creation of custom sets of hand-picked attributes that are relevant for specific audiences. (e.g. "customer - delivery details" that would include just their name and last known delivery address). This is very similar to a database view.
* ''Hierarchies''
* ''Business Rules'' can be created and applied against model data to ensure that custom business logic is adhered to. In order to be committed into the system data must pass all business rule validations applied to them. e.g. Within the Customer Entity you may want to create a business rule that ensures all members of the 'Country' Attribute contain either the text "USA" or "Canada". The Business Rule once created and ran will then verify all the data is correct before it accepts it into the approved model.
* ''Versions'' provide system owners / administrators with the ability to Open, Lock or Commit a particular version of a model and the data contained within it at a particular point in time. As the content within a model varies, grows or shrinks over time versions provide a way of managing metadata so that subscribing systems can access to the correct content.
Line 31 ⟶ 30:
==External links==
*[
*[https://msdn.microsoft.com/en-us/library/ff929136.aspx What's New in Master Data Services (MDS)]
[[Category:Data management]]
| |||