Test Me

Lab 05
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
Developing a SQL Server 2016 Master Data Services Solution
Connecting to the Virtual Machine

In this exercise, you will use the lab hosting portal to connect to the virtual machine, and optimize the
virtual machine environment for your language and location.
Signing In
In this task, you will sign in to the virtual machine.
1. To sign in to the virtual machine, using the portal menu, click Commands, and then select
Ctrl + Alt + Delete.
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.
Updating the Virtual Machine Language

In this task, you will sign in to the virtual machine by using the on-screen keyboard, and then update
the virtual machine language. This is important to ensure that your keyboard characters are correctly
received by the virtual machine.
1. Located at the bottom-left of the virtual machine screen, click Ease of Access, and then select
On-Screen Keyboard.
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.
3. Submit the password.

4. Once signed in, to add a new language, on the taskbar, click the Windows button.
5. In the Start screen, click the Control Panel tile.
6. In the Control Panel window, from inside the Clock, Language, and Region group, click
Change Input Methods.
7. In the Language window, click Add a Language.
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.
Changing the Screen Resolution (Optional)

It is recommended that you change the virtual machine screen resolution to take full advantage of your
screen size.
1. Using the portal menu, click Display, and then select Full Screen.
2. First, notice that the portal left pane can be resized.
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.
Changing the Clock (Optional)

Changing the clock is for your convenience only, and therefore this task is optional.
1. In the taskbar, click the clock, and then select Change Date and Time Settings.
2. In the Date and Time window, click Change Time Zone.
3. In the Time Zone Settings window, in the Time Zone dropdown list, select your time zone.
4. Click OK.
5. In the Date and Time window, click OK.
Ending the Lab Session
In this task, you will explore how to end the lab sessionwhen you are ready to do so.
1. At the top right-corner of the portal, click Exit, and then select End Lab.
2. When prompted to end the lab, click Yes, End My Lab.
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.
You are now ready to commence the lab.
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.
2. In the File Explorer window, navigate to the D:\SQLServer2016BI\Lab05\Assets folder.

3. Right-click the Startup.cmd file, and then select Open.
4. In the Command window, when prompted to press any key to continue, press any key.
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.
2. In Internet Explorer, use to favorites bar to navigate to Master Data Manager.
3. On the web application home page, click the System Administration tile.
4. To create a model, click Add.
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
Creating and Managing Entities in Excel

In this exercise, you will create and manage four master data entities by using the Master Data
Services Add-in for Excel. You will also add a new member to two of the entities.
When creating the entities in this exercise it is very important that you name them as instructed. The
final exercise in this lab includes a pre-built solution that references these entities by name.
Creating the CountryRegion Entity
In this task, you will create the CountryRegion entity.
1. To open Excel, on the taskbar, click the Excel shortcut.
2. If prompted to activate Office, click Cancel.
3. To open an existing workbook, in the Recent pane (located at the left), click
Open Other Workbooks.
12
4. Click Browse.
5. In the Open window, navigate to the D:\SQLServer2016BI\Lab05\Assets folder, select the

Geography.xlsx file, and then click Open.
6. In the workbook, notice the three worksheets, each representing a different geographic entity.
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.
8. In the Manage Connections window, click New.

9. In the Add New Connection window, in the Description box, enter MDS.
13
10. In the MDS Server Address box, replace the text with http://localhost:90.
11. Click OK.

12. In the Manage Connections window, click Connect.
13. In the Master Data Explorer pane (located at the right), in the Model dropdown list, select
AdventureWorksBI.
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
16. In the Create Entity window, configure the following properties.

Property
Value
Range
$A$1:$D$7 (set by default)
Model
AdventureWorksBI
New Entity Name
CountryRegion
Code
CountryRegionCode
Name
EnglishCountryRegionName
Every entity must define a code attribute consisting of unique values.

17. Click OK.
18. Notice the addition of the CountryRegion 1 worksheet.
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.
20. Select the FrenchCountryRegionName table header (cell P2).

21. On the Master Data ribbon, from inside the Build Model group, select Attribute Properties.
15
22. In the Attribute Properties window, modify the Maximum Length property to 50.
23. Click OK.

24. Modify also the SpanishCountryRegionName attribute to a maximum length of 50.
25. To delete the CountryRegion 1 worksheet, right-click the CountryRegion 1 worksheet, and then
select Delete.
26. When prompted to confirm the deletion, click Delete.
This action does not delete the published entity or its members.
Creating the StateProvince Entity
In this task, you will create the StateProvince entity. You will also create the SalesTerritoryRegion
entity based on the existing values in the StateProvince entitys SalesTerritoryRegion attribute.
1. Select the StateProvince worksheet.
2. Create a new entity based on the following properties.

Property
Value
Range
$A$1:$E$72 (set by default)
Model
AdventureWorksBI
New Entity Name
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.
10. In the Settings window, select the Data page.
11. In the Display Format dropdown list, select Code.
12. Click OK.
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.
15. Modify the StateProvinceCode attribute to a maximum length of 3.
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
Publishing a New StateProvince Member

In this task, you will publish a new StateProvince member.
1. Scroll to the bottom of the table, and then select cell N74.
2. Enter the following values in row 74.
If necessary, you can widen the columns.
Attribute
Value
Name
Western Australia
Code
AU-WA
CountryRegionCode
AU (use the dropdown list)
StateProvinceCode
WA
SalesTerritoryRegion
Australia (use the dropdown list)
3. Ensure that you press Enter to register the data input.

4. To publish the new member, on the Master Data ribbon, from inside the Publish and Validate
group, select Publish.
5. In the Publish and Annotate window, click Publish.

6. Notice that the master list refreshes.
7. In row 3, notice the addition of the new member.
8. Delete the StateProvince 1 worksheet.
21
Creating the City Entity

In this task, you will create the City entity.
1. Select the City worksheet.
2. Create a new entity based on the following properties.

Property
Value
Range
$A$1:$D$656 (set by default)
Model
AdventureWorksBI
New Entity Name
City
Code
Generate Code Automatically
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
5. Modify the PostalCode attribute to a maximum length of 15.
6. Modify the IpAddressLocator attribute to a maximum length of 15.
Publishing a New City Member

In this task, you will publish a new City member.
1. Scroll to the bottom of the table, and then select cell N658.
2. Enter the following values in row 658.
Attribute
Value
Name
Perth
Code
(Do not enter a valuea unique code will be automatically generated)
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
3. Ensure that you press Enter to register the data input.

4. Publish the new member.
5. In row 3, notice the addition of the new member.
Finishing Up
In this task, you will close Excel.
1. To close Excel, click the X button located at the top right corner.
2. When prompted to save changes, click Dont Save.

The remaining tasks for this lab will manage and explore the model by using the Master Data
Manager Web application.
24
Managing Master Data

In this exercise, you will use the Master Data Manager Web application to explore the members from
the StateProvince entity, and then apply a data correction to one member.
Note that all of the tasks in this exercise could also be completed by using the Master Data Services
Add-in for Excel.
Exploring the StateProvince Entity
In this task, you will explore the StateProvince members, and then apply a data correction to one of
the members.
1. To return to the Master Data Manager home page, click the SQL Server 2016 banner text.
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
3. Click the Entities menu, and then select StateProvince.
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.
6. Select the Washington member (row).

7. In the details pane (located at the right), in the SalesTerritoryRegion dropdown list, select
Northwest {Northwest}.
26
8. In the Annotations box, enter Error correction.
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.
13. Click Close.
27
Creating a Business Rule

In this exercise, you will create a business rule for the City entity. You will then explore the members
of the City entity, apply business rules, and then review and correct invalid members.
Creating a Business Rule
In this task, you will create a business rule for the City entity to ensure that valid IP addresses are
stored.
1. Return to the Master Data Manager home page.
2. Click the System Administration tile.
3. Click the Manage menu, and then select Business Rules.
28
4. Ensure that the City entity is selected.
5. To create a business rule, click Add.
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
8. In the Create Action dialog window, configure the following properties.

For convenience, the attribute value (regular expression) can be copied from the
D:\SQLServer2016BI\Lab05\Assets\Snippets.txt file.
9. Click Save.
10. In the Add Business Rule dialog window, 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.
13. To publish the business rule, click Publish All.
14. When prompted to confirm, click OK.
31
Applying Business Rules

In this task, you will apply business rules to the City entity.
2. Click the Explorer tile.
3. Click the Entities menu, and then select City.
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.
8. When prompted to confirm, click OK.

9. Check the entity validation status again, and notice that two member failed validation.
10. Click Close.

11. To review the two members with invalid IP addresses, click Filter.
33
12. Configure the filter based on the following.
13. Click Apply.
14. Notice the two cities with invalid IP addresses.
Applying Data Corrections

In this task, you will apply data corrections to the invalid City members.
1. Select the Melbourne member.
2. In the details pane, in the IpAddressLocator box, modify the value to 198.51.100.36.
3. In the Annotations box, enter Error correction.
4. Click OK.
5. Review the member history.
6. Modify also the IP address for San Francisco to 192.0.2.107.
7. Check the status of all members, and verify that all members have successfully been validated.
8. Click Close.
34
Creating a Derived Hierarchy

In this exercise, you will create a derived hierarchy to enable navigation between the different
geographic entities.
Creating a Derived Hierarchy
In this task, you will create a derived hierarchy to enable navigation between the different geographic
entities.
2. Click the System Administration tile.
3. Click the Manage menu, and then select Derived Hierarchies.
35
4. To create a derived hierarchy, click Add.
5. In the Derived Hierarchy Name box, enter Geography.

6. Click the Save Derived Hierarchy button.
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.
Hierarchies are assembled from the lowest to highest levels.

8. To add the next level to the hierarchy, drag StateProvince on top of the Drop Parent Here node.
9. Add the CountryRegionCode as the third level.
10. Verify that the hierarchy levels look like the following.
36
11. To rename the first level, select the CountryRegionCode level.
12. In the Display Name box, replace the text with Country.
13. Click the Save Selected Hierarchy Item button.
14. Rename also the StateProvince level to State.

15. To preview the hierarchy, in the Preview section, expand AU {Australia}, and then expand AUWA {Western Australia}.
37
Creating Subscription Views

In this exercise, you will create four subscription views to enable the export of the master data. These
views will be used in the next exercise by an Integration Services package.
Creating Subscription Views
In this task, you will create subscription views for the geographic entities.
2. Click the Integration Management tile.
3. On the menu, select Create Views.
4. To create a subscription view, click Add.
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.
7. Create a second subscription view, based on the following.

Property
Value
Name
Geography_CountryRegion
Data Source
Entity
Derived Hierarchy
CountryRegion
8. Create two additional subscription views, based on the following.

Subscription View Name
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
Reviewing the Subscription Views

In this task, you will review the subscription views created in the MDS repository database.
1. To open SQL Server Management Studio, on the taskbar, click the
SQL Server Management Studio shortcut.
2. In the Connect to Server window, set the following connection values.
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
Extracting Master Data

In this exercise, you will open, review and then execute an Integration Services package designed to
load the DimGeography dimension table.
Reviewing the Integration Services Package
In this task, you will open and review the LoadDimGeography package.
1. To open SQL Server Data Tools (Visual Studio), on the taskbar, click the Visual Studio program
shortcut.
2. On the File menu, select Open | Project/Solution.

3. In the Open Project window, navigate to the
D:\SQLServer2016BI\Lab05\Assets\AdventureWorksBI folder, select the
AdventureWorksBI.sln file, and then click Open.
If Visual Studio crashes, close Visual Studio and re-open the solution.
4. When prompted for the encryption password, enter Pass@word1, and then click OK.
5. In Solution Explorer (located at the right), review the project items, and notice that the project
contains the LoadDimGeography package.
6. Right-click the LoadDimGeography package, and then select Open.

7. Review the comments in the control flow design.
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.
Executing the Package

In this task, you will execute the LoadDimGeography package.
1. To execute the package, in Solution Explorer, right-click the LoadDimGeography package, and
then select Execute Package.
2. Review the data in the two data viewer windows that open.
The window titled New Output Data Viewer displays any new cities added. Recall that the city of
Perth was added.
The window titled Changing Attribute Updates Output Data Viewer displays 44 rows
representing the changes made to the Melbourne and San Francisco IP addresses, and all 42
Washington cities which have had their sales territory region changed to Northwest.
3. To close the data view windows, click the X button located at the top right corner.
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.
5. To return to design mode, on the Debug menu, select Stop Debugging.
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
SQL Server 2016 CTP 3.2
20-MAR-2016
Peter Myers
SQL Server 2016 RC1
09-APR-2016
Peter Myers
SQL Server 2016 RC2
24-APR-2016
Peter Myers
SQL Server 2016 RC2

Connecting to the Virtual Machine exercise added
10-JUL-2016
Peter Myers
SQL Server 2016 GA

Master Data Services Add-in for Excel v13.0.1601.5
48

Test Me

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Test Me

Transféré par

Droits d'auteur :

Formats disponibles

Lab 05

Developing a SQL Server 2016

Developing a SQL Server 2016 Master Data Services Solution

Connecting to the Virtual Machine

Developing a SQL Server 2016 Master Data Services Solution

Updating the Virtual Machine Language

3. Submit the password.

Developing a SQL Server 2016 Master Data Services Solution

5. In the Start screen, click the Control Panel tile.

7. In the Language window, click Add a Language.

Developing a SQL Server 2016 Master Data Services Solution

Changing the Screen Resolution (Optional)

2. First, notice that the portal left pane can be resized.

Developing a SQL Server 2016 Master Data Services Solution

Changing the Clock (Optional)

2. When prompted to end the lab, click Yes, End My Lab.

Developing a SQL Server 2016 Master Data Services Solution

You are now ready to commence the lab.

Developing a SQL Server 2016 Master Data Services Solution

2. In the File Explorer window, navigate to the D:\SQLServer2016BI\Lab05\Assets folder.

Developing a SQL Server 2016 Master Data Services Solution

2. In Internet Explorer, use to favorites bar to navigate to Master Data Manager.

4. To create a model, click Add.

Developing a SQL Server 2016 Master Data Services Solution

Developing a SQL Server 2016 Master Data Services Solution

Creating and Managing Entities in Excel

2. If prompted to activate Office, click Cancel.

Developing a SQL Server 2016 Master Data Services Solution

5. In the Open window, navigate to the D:\SQLServer2016BI\Lab05\Assets folder, select the

8. In the Manage Connections window, click New.

Developing a SQL Server 2016 Master Data Services Solution

11. Click OK.

Developing a SQL Server 2016 Master Data Services Solution

16. In the Create Entity window, configure the following properties.

$A$1:$D$7 (set by default)

New Entity Name

Every entity must define a code attribute consisting of unique values.

20. Select the FrenchCountryRegionName table header (cell P2).

Developing a SQL Server 2016 Master Data Services Solution

23. Click OK.

2. Create a new entity based on the following properties.

$A$1:$E$72 (set by default)

New Entity Name

Developing a SQL Server 2016 Master Data Services Solution

Developing a SQL Server 2016 Master Data Services Solution

10. In the Settings window, select the Data page.

11. In the Display Format dropdown list, select Code.

12. Click OK.

Developing a SQL Server 2016 Master Data Services Solution

15. Modify the StateProvinceCode attribute to a maximum length of 3.

Developing a SQL Server 2016 Master Data Services Solution

Developing a SQL Server 2016 Master Data Services Solution

Publishing a New StateProvince Member

AU (use the dropdown list)

Australia (use the dropdown list)

3. Ensure that you press Enter to register the data input.

5. In the Publish and Annotate window, click Publish.

8. Delete the StateProvince 1 worksheet.

Developing a SQL Server 2016 Master Data Services Solution

Creating the City Entity

2. Create a new entity based on the following properties.

$A$1:$D$656 (set by default)

New Entity Name

Generate Code Automatically