Professional Documents
Culture Documents
Developing A SQL Server 2016 Master Data Services Solution
Developing A SQL Server 2016 Master Data Services Solution
Overview
The estimated time to complete this lab is 45 minutes
In this lab you will develop a SQL Server 2016 Master Data Services solution to store and manage
geographic master data.
This will involve using two tools to create and manage the solution. You will first use the Master Data
Services Add-in for Excel to create entities, and to also insert new members. You will then use the
Master Data Manager Web application to explore, review and maintain members, and also to create a
business rule and a derived hierarchy. Finally, you will create several subscription views that will be
used by a pre-developed SQL Server 2016 Integration Services solution to populate a dimension
table.
You will learn how to:
Use Master Data Manager to create a model
Use Master Data Services Add-in for Excel to create entities and define attributes
Use both Master Data Manager and Excel to explore, review and maintain master data
Use Master Data Manager to create business rules, derived hierarchies and subscription views
Use Integration Services to source master data to populate a data warehouse table
2. In the password box, enter Pass@word1 (do not enter the period), and then click Submit.
If you are not using a US English keyboard, the password you enter may not be correctly received
by the virtual machine. You must complete the following task to sign in, and then update the virtual
machine language.
Note: For lab users with English keyboards, if the @ symbol is above the 2, then your keyboard is
a US English keyboard, and you should not complete the following task.
2. Use the on-screen keyboard to enter the password Pass@word1. (Do not enter the period.)
Tip: To reveal the input password before submitting, click the following.
6. In the Control Panel window, from inside the Clock, Language, and Region group, click
Change Input Methods.
8. In the Add Languages window, locate and select your language, and then click Add (or Open).
If the selected language has regional variants, you will be directed to the Regional Variants
window, in which case, select a variant, and then click Add.
9. Close the Language window.
10. In the taskbar, click ENG, and then select your language.
3. Resize the width of the pane, with the aim of arriving at a minimum width that allows the font size
of the content (lab manual) to remain easily readable.
Tip: Less width occupied by the pane allows for more room for the virtual machine screen.
4. In the virtual machine screen, right-click the desktop, and then select Screen Resolution.
5. In the Screen Resolution window, in the Resolution dropdown list, select a higher resolution.
1024 x 768 is the recommended minimum, but use a higher resolution if this fits your screen size.
6. Click Apply.
7. If the entire virtual machine screen is fully visible within the portal, click Keep Changes, otherwise,
click Revert, and try a different resolution.
3. Once redirected to the evaluation form, please take a few moments to complete and submit your
evaluation of this labyour feedback assists us to deliver a great lab experience.
Getting Started
In this exercise, you will execute a T-SQL script to prepare the AdventureWorksDW2016 database
for this lab.
Getting Started
In this task, you will execute a T-SQL script to prepare the AdventureWorksDW2016 database for
this lab.
1. To open File Explorer, on the taskbar, click the File Explorer shortcut.
Creating a Model
In this exercise, you will use Master Data Manager to create the AdventureWorksBI model.
Creating a Model
In this task, you will use Master Data Manager to create the AdventureWorksBI model.
1. To open Internet Explorer, on the taskbar, click the Internet Explorer shortcut.
3. On the web application home page, click the System Administration tile.
10
5. In the Add Model panel (located at the right), in the Name box, enter AdventureWorksBI, and
then uncheck the Create Entity with Same Name as Model checkbox.
6. Click Save.
7. In the model list, verify that the model has been successfully created.
11
3. To open an existing workbook, in the Recent pane (located at the left), click
Open Other Workbooks.
12
4. Click Browse.
7. On the Master Data ribbon, from inside the Connect and Load group, click the down-arrow below
the Connect button, and then select Manage Connections.
13
10. In the MDS Server Address box, replace the text with http://localhost:90.
14. To create a new entity, first ensure the CountryRegion worksheet is in focus, and that the entire
table (range A1:D7) is selected.
15. On the Master Data ribbon, from inside the Build Model group, select Create Entity.
14
Value
Range
Model
AdventureWorksBI
CountryRegion
Code
CountryRegionCode
Name
EnglishCountryRegionName
This worksheet includes a table that is the query result of the newly created entity. The table can
be filtered, sorted and the master list values modified. Modified data can be published back to the
server. You will work with this functionality later in this exercise.
19. In the Master Data Explorer pane, notice also the addition of the CountryRegion entity.
15
22. In the Attribute Properties window, modify the Maximum Length property to 50.
Value
Range
Model
AdventureWorksBI
StateProvince
Code
StateProvinceKey
Name
StateProvinceName
16
3. In the Master Data Explorer pane, verify the addition of the StateProvince entity.
4. Edit the attribute properties for the CountryRegionCode attribute (column P).
5. To create a domain lookup, in the Attribute Type dropdown list, select
Constrained List (Domain-Based).
6. In the Populate the Attribute with Values From dropdown list, select CountryRegion.
7. Click OK.
17
8. Select cell P3, and then notice that the CountryRegionCode attribute values are now available
for selection in a dropdown list.
The available values in the dropdown list are sourced from the CountryRegion entity created in
the previous task. The list presents the member code followed by the member name presented in
braces ({}), and are sorted by the member name.
9. To view only the code value in the list, on the Master Data ribbon, from inside the Options group,
select Settings.
18
13. To reload the master list, on the Master Data ribbon, from inside the Connect and Load group,
select Refresh.
14. Notice that the CountryRegionCode available values are described only by the code.
19
16. Configure the SalesTerritoryRegion attribute to create a domain lookup to a new entity based on
the attribute values.
17. In the Master Data Explorer pane, verify the addition of the SalesTerritoryRegion entity.
18. Select cell R3, and then notice that the SalesTerritoryRegion attribute values are now available
for selection in a dropdown list.
20
Value
Name
Western Australia
Code
AU-WA
CountryRegionCode
StateProvinceCode
WA
SalesTerritoryRegion
21
Value
Range
Model
AdventureWorksBI
City
Code
Name
City
3. In the Master Data Explorer pane, verify the addition of the City entity.
4. Configure the StateProvince attribute to create a domain lookup to the StateProvince entity.
22
Value
Name
Perth
Code
StateProvince
AU-WA (use the dropdown list, with the item located close to the end of the list)
PostalCode
6000
IpAddressLocator
203.0.113.149
23
Finishing Up
In this task, you will close Excel.
1. To close Excel, click the X button located at the top right corner.
24
Tip: You can also click the Home link, just beneath the banner text.
2. On the Master Data Manager home page, click the Explorer tile.
25
4. Use the page navigation controls (located at the bottom-right corner of the data grid) to locate the
Washington member.
5. Notice that the state of Washington has been incorrectly assigned to the Northeast region.
26
9. Click OK.
10. To review the changes made to the member, click the View History link.
11. Review the history available for the Washington member in the grid.
Each of the revisions represents a change made to the Washington member. The first revision
was when the member was added, with each of the following three revisions representing the
addition of the attribute values (CountryRegionCode, StateProvinceCode and
SalesTerritoryRegion). The last revision was for the SalesTerritoryRegion update that you just
made.
12. Review also the annotation, and notice that it is recorded together with the user account and time
stamp.
27
28
6. In the Add Business Rule dialog window, in the Name box, enter Valid IP Address.
7. To add an action, inside the Then group, click the Add link.
29
9. Click Save.
30
11. In the business rules list, verify that the business rule has been successfully created.
12. To review the business rule definition, in the list, select the Valid IP Address business rule.
31
4. To check the entity validation status, to the right of Apply Rules, click the down-arrow, and then
select Check Status.
32
5. In the dialog window, notice that all members are not yet validated.
6. Click Close.
7. To apply business rules to all members, to the right of Apply Rules, click the down-arrow, and
then select Apply to All.
33
8. Click Close.
34
35
7. To assemble the hierarchy, in the Available Entities and Hierarchies section, select and then
drag City on top of the Drop Parent Here node.
36
12. In the Display Name box, replace the text with Country.
37
38
5. In the Create Subscription View pane (located at the right), configure the following properties.
It is important that you name the subscription views correctly. The views will be queried by a predeveloped Integration Services package in the next exercise.
Property
Value
Name
Geography
Data Source
Derived Hierarchy
Derived Hierarchy
Geography
Level
6. Click Save.
Value
Name
Geography_CountryRegion
Data Source
Entity
Derived Hierarchy
CountryRegion
Entity
Geography_StateProvince
StateProvince
Geography_City
City
9. Verify that the following four subscription views have been added, and in particular, verify that
each subscription view is for the correct data source.
39
3. Click Connect.
4. In Object Explorer (located at the left), expand Databases | MDS | Views.
5. Notice the four subscription views at the top of the view list.
6. Right-click the mdm.Geography view, and then select Select Top 1000 Rows.
7. Review the query result.
8. Expand mdm.Geography_City | Columns.
40
9. Review the available columns in the view, consisting of version columns, the attributes, user and
time stamps, and validation status.
This view represents a simplified way to access the master data in an entity (or hierarchy). These
views will be used in the next exercise to extract the master data and load it into the data
warehouse dimension table.
10. Query also the mdm. Geography_City view, and review the query result.
41
42
8. Right-click the Load DimGeography Data Flow task, and then select Edit.
If you notice any error icons, it is likely that the subscriptions views were not created, or named
correctly. In this case, return to the previous exercise and address any differences. Then close
and re-open the LoadDimGeography package.
9. Review the comments related to each data flow component.
You can also open the components to fully understand the package designbut do not modify
any properties.
10. Notice that there are two data viewers to assist reviewing the data changes detected by the Slowly
Changing Dimension transformation.
43
4. In the data flow of the LoadDimGeography package, review the statistics that describe that 656
rows were passed into the Slowly Changing Dimension transformation, and the rows passed out
to the two output components.
44
Finishing Up
In this exercise, you will finish up by undoing the configurations made in this lab, and by closing
opened applications.
There is no need to complete this exercise if you do not plan to do any more labs in this Virtual
Machine session.
Finishing Up
In this task, you will finish up by undoing the configurations made in this lab, and by closing opened
applications.
1. To close Visual Studio, on the File menu, select Exit.
2. To close SQL Server Management Studio, on the File menu, select Exit.
3. In Master Data Manager, in System Administration, select the AdventureWorksBI model, and
then click Delete.
4. When prompted to confirm the deletion, click OK.
5. Close the Internet Explorer window.
6. In a File Explorer window, navigate to the D:\SQLServer2016BI\Lab05\Assets folder.
7. Right-click the Cleanup.cmd file, and then select Open.
8. In the Command window, when prompted to press any key to continue, press any key.
9. Close the File Explorer window.
45
Summary
In this lab you developed a SQL Server 2016 Master Data Services solution to store and manage
geographic master data.
This involved using two tools to create and manage the solution. You first used the Master Data
Services Add-in for Excel to create entities, and to also insert new members. You then used the
Master Data Manager Web application to explore, review and maintain members, and also to create a
business rule and a derived hierarchy. Finally, you created several subscription views that were used
by a pre-developed SQL Server 2016 Integration Services solution to populate a dimension table.
46
Terms of Use
2015-2016 Microsoft Corporation. All rights reserved.
By using this hands-on lab, you agree to the following terms:
The technology/functionality described in this hands-on lab is provided by Microsoft Corporation in a
sandbox testing environment for purposes of obtaining your feedback and to provide you with a
learning experience. You may only use the hands-on lab to evaluate such technology features and
functionality and provide feedback to Microsoft. You may not use it for any other purpose. Without
written permission, you may not modify, copy, distribute, transmit, display, perform, reproduce,
publish, license, create derivative works from, transfer, or sell this hands-on lab or any portion thereof.
COPYING OR REPRODUCTION OF THE HANDS-ON LAB (OR ANY PORTION OF IT) TO ANY
OTHER SERVER OR LOCATION FOR FURTHER REPRODUCTION OR REDISTRIBUTION
WITHOUT WRITTEN PERMISSION IS EXPRESSLY PROHIBITED.
THIS HANDS-ON LAB PROVIDES CERTAIN SOFTWARE TECHNOLOGY/PRODUCT FEATURES
AND FUNCTIONALITY, INCLUDING POTENTIAL NEW FEATURES AND CONCEPTS, IN A
SIMULATED ENVIRONMENT WITHOUT COMPLEX SET-UP OR INSTALLATION FOR THE
PURPOSE DESCRIBED ABOVE. THE TECHNOLOGY/CONCEPTS REPRESENTED IN THIS
HANDS-ON LAB MAY NOT REPRESENT FULL FEATURE FUNCTIONALITY AND MAY NOT WORK
THE WAY A FINAL VERSION MAY WORK. WE ALSO MAY NOT RELEASE A FINAL VERSION OF
SUCH FEATURES OR CONCEPTS. YOUR EXPERIENCE WITH USING SUCH FEATURES AND
FUNCITONALITY IN A PHYSICAL ENVIRONMENT MAY ALSO BE DIFFERENT.
FEEDBACK If you give feedback about the technology features, functionality and/or concepts
described in this hands-on lab to Microsoft, you give to Microsoft, without charge, the right to use,
share and commercialize your feedback in any way and for any purpose. You also give to third parties,
without charge, any patent rights needed for their products, technologies and services to use or
interface with any specific parts of a Microsoft software or service that includes the feedback. You will
not give feedback that is subject to a license that requires Microsoft to license its software or
documentation to third parties because we include your feedback in them. These rights survive this
agreement.
MICROSOFT CORPORATION HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH
REGARD TO THE HANDS-ON LAB, INCLUDING ALL WARRANTIES AND CONDITIONS OF
MERCHANTABILITY, WHETHER EXPRESS, IMPLIED OR STATUTORY, FITNESS FOR A
PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. MICROSOFT DOES NOT MAKE ANY
ASSURANCES OR REPRESENTATIONS WITH REGARD TO THE ACCURACY OF THE RESULTS,
OUTPUT THAT DERIVES FROM USE OF THE VIRTUAL LAB, OR SUITABILITY OF THE
INFORMATION CONTAINED IN THE VIRTUAL LAB FOR ANY PURPOSE.
DISCLAIMER This lab contains only a portion of new features and enhancements in Microsoft Power
BI. Some of the features might change in future releases of the product.
47
Document Version
#
Date
Author
Comments
28-DEC-2015
Peter Myers
20-MAR-2016
Peter Myers
09-APR-2016
Peter Myers
24-APR-2016
Peter Myers
10-JUL-2016
Peter Myers
48