Documente Academic
Documente Profesional
Documente Cultură
This practice project is designed to test your ability to configure and deploy a
basic MicroStrategy business intelligence environment. You will use your
knowledge of MicroStrategy Architect and MicroStrategy Desktop to create a
project and design reports that run against the MicroStrategy Tutorial data
warehouse. This project will assist you in preparing for specific sections of the
MicroStrategy Certified Developer (MCD) Certification. However, it does not
provide practice on every subject matter that is required to successfully complete
the MCD Certification. To achieve MCD Certification, you also need to master the
knowledge attained through the Project Designer, Report Developer, and
Platform Administrator focus area certifications.
The Project Design section of this document contains requirements and detailed
instructions on how you satisfy the requirements. We recommend that you try to
complete the entire project using only the requirements. Use the detailed
instructions only if you need assistance. If you need to use the detailed
instructions to complete a task, we recommend that you redo the task until you
no longer need assistance. Remember, this is a practice project. The actual MCD
Certification will not include step-by-step instructions.
This project contains information that is covered in the Certified Project Designer
certification and the Certified Report Developer certification. The Certified
Project Designer certification contains the MicroStrategy Architect: Project
Design course and the MicroStrategy Desktop: Reporting Essentials course and
is the first week of the MCD Program. The Certified Report Developer
certification contains the MicroStrategy Report Services: Document Essentials
course and the MicroStrategy Desktop: Advanced Reporting course and is the
second week of the MCD Program. MicroStrategy Education recommends that
you attempt this practice project after completing the Certified Report Developer
certification. If you are completing the entire 3.5 week MCD Program at one time
you should attempt this project after the finishing the second week.
Project Guidelines:
Try to complete the entire project without using the detailed instructions.
(The MCD Certification does not contain instructions on how to complete a
task.)
Remember, this is a practice project. It does not include all topics that are
covered on the actual MCD.
PROJECT DESIGN
Although this project assumes that you have already installed Architect and
Desktop Designer, we recommend that you understand how to install specific
MicroStrategy products.
This phase of the project covers concepts from the MicroStrategy Architect:
Project Design and the MicroStrategy Desktop: Reporting Essentials courses.
After completing this phase of the project, you will be ready to begin report
development.
This practice project is not comprehensive and does not cover all topics
that are required to successfully complete the actual MCD project. In
addition, this practice project contains step-by-step directions. The MCD
project does not contain step-by step instruction.
Before you can begin project creation, you need to create your MicroStrategy
metadata database and establish connections to both the metadata database
and the data warehouse. The following pages list the steps to create the
metadata database and connect to the metadata database and the data
warehouse.
If you are using Microsoft Access 2003, on the File menu, select New.
Click OK.
5. Click Create.
1. On the Windows Start Menu, point to Settings, and select Control Panel.
4. In the ODBC Data Source Administrator, select the System DSN tab.
6. In the Create New Data Source window, select Microsoft Access Driver
(*.mdb).
7. Click Finish.
8. In the ODBC Microsoft Access Setup window, in the Data Source Name
box, enter Practice_Tutorial_MD_DSN.
In the ODBC Microsoft Access Setup window, on the System DSN tab,
you should see your new metadata DSN.
Create a 2-tier project source that points to your metadata database. Name the
project source Tutorial Practice Project Source.
Before you create the project source, you must create the MicroStrategy
metadata shell. You can complete both steps using the MicroStrategy
Configuration Wizard.
3. Click Next.
5. Click Next.
7. Click Next.
8. Click Finish.
o Wait while the configuration wizard configures the metadata
database.
12. For Project Source Name, enter Practice Tutorial Project Source. Select
Direct (2-tier).
19. When notified that the configuration was successful, click Close.
This project uses the Practice Tutorial_WH that is included with the MCD Project
Practice, Tutorial Project online companion course. You can find the Practice
Tutorial_WH on the Supporting Documents page. Complete the following steps
to download the Practice Tutorial_WH.
3. In the Folder List, expand the Practice Tutorial Project Source 2-tier
project source you created earlier.
6. Click OK.
7. When informed that no projects were returned by your project source, click
OK.
Note: You have not yet created any MicroStrategy projects in this
project source.
11. On the File menu, point to New, and then select Database Instance
22. In the Database Connections window, under Default database login name,
ensure that your new Practice Tutorial Login database login is selected.
This completes the definition of your database instance. The information you just
created is encrypted and saved to the metadata.
Project Creation
Now that you have configured your metadata and set up the connections to the
metadata and data warehouse, you are ready to create your MicroStrategy
project using Architect.
Note: This document provides steps on how to create a project using the Project
Creation Assistant. Be aware that you can create an incomplete project
definition, save it, and complete it later. However, if you exit the Project Creation
Assistant early, you cannot use it again to complete the project definition. As
such, it is strongly recommended that you create your initial project definition in
one sitting.
Note: This practice project is not comprehensive and does not cover all topics
that are required to successfully complete the actual MCD project. In addition,
this practice project contains step-by-step directions. The MCD project does not
contain step-by step instruction.
Create a new project inside of the Practice Tutorial Project Source. Name the
project Practice Tutorial Project.
2. In the Project Creation Assistant, to the left of Create project, click >.
4. Click OK.
Architect now populates the metadata tables with initial project data. When
project initialization is complete, the Project Creation Assistant returns with a
green check mark next to the Create project step.
Using the Schema in Appendix B, select the tables to be used in the project.
Be sure to include all tables diagramed in Appendix B.
1. In the Project Creation Assistant, to the left of Select tables from the
Warehouse Catalog, click >.
3. Click OK.
You can use the CTRL or SHIFT keys to select multiple tables at
once.
LU_MONTH_OF_YEAR STATE_REGION_MNTH_SLS
5. After you have added all the tables to the project, click Save and
Close.
The Project Creation Assistant returns with a green check mark next to the
Select tables from the Warehouse Catalog step.
3. Facts
Next, create five facts for you project using the following table. Name each
fact according to the table and map the facts to the appropriate data
warehouse tables.
Facts
1. In the Project Creation Assistant, to the left of Create facts, click >.
You can use the CTRL or SHIFT keys to select multiple columns at
once.
4. Click Next.
5. After reviewing the list of facts that you are about to create, click
Finish.
The Project Creation Assistant returns with a green check mark next to the
Create facts step.
4. Attributes
Take note of the following relationships that are not explicitly defined in the
logical data model.
Cells with bold text indicate a compound key or a relationship type that
is something other than one-to-many.
You can use the CTRL or SHIFT keys to select multiple ID columns
at once.
Attributes
Attribute
Lookup Table ID Column DESC Column Children
Name
Birth Date LU_Employee Birth_Date Use ID as description Employee
Brand LU_Brand Brand_ID Brand_Desc Item
Call Center LU_Call_Ctr Call_Ctr_ID Center_Name Employee
Catalog LU_Catalog Cat_ID Cat_Desc Item(M:M)
Category LU_Category Category_ID Category_Desc Subcategory
Region and
Country LU_Country Country_ID Country_Name Distribution
Center
Customer City LU_Cust_City Cust_City_ID Cust_City_Name Customer
Attribute
Lookup Table ID Column DESC Column Children
Name
Income
LU_Income Income_ID Bracket_Desc Customer
Bracket
Item LU_Item Item_ID Item_Name NONE
Manager LU_Manager Manager_ID Mgr_Last_Name Call Center(1:1)
Month LU_Month Month_ID Month_Desc Day
Month of Year LU_Month_of_Year Month_of_Year Month_of_Year_Name Month
Order Order_Detail Order_ID Use ID as description NONE
Promotion LU_Promotion Promo_Sale_ID Promo_Sale Item, Day
Promotion
LU_Promo_Type Promo_Type_ID Promo_Type_Desc Promotion
Type
Payment
LU_Pymt_Type Pymt_Type Pymt_Desc Order
Method
Quarter LU_Quarter Quarter_ID Quarter_Desc Month
Region LU_Region Region_ID Region_Name Call center
Shipper LU_Shipper Shipper_ID Shipper_Desc Order
Subcategory LU_Subcateg Subcat_ID Subcat_Desc Item
Supplier LU_Supplier Supplier_ID Supplier_Name Item
Year LU_Year Year_ID Use ID as description Quarter
Click Add.
Select COUNTRY_ID and while holding down the CTRL key, select
DIST_CTR_ID.
- Ensure that you do not have the first column (Address) selected
because it will cause an error.
Click OK.
- Under Compound Attributes, you should now see your
Distribution Center attribute. You can expand it to see its
compound ID columns.
5. Click Next.
You specify the lookup table for Distribution Center in a later step.
8. Click Next.
Click OK.
11. Specify the children for each attribute according to the Attributes table
by doing the following:
13. After reviewing the list of attributes you are about to create, click
Finish.
You should now see Practice Tutorial Project under Practice Tutorial Project
Source.
Using the Fact Editor, create two additional facts according to the table below:
Source
Fact Name Fact Expressions
Tables
([QTY_SOLD] *
([UNIT_PRICE] - ORDER_DETAIL
DISCOUNT))
CITY_CTR_SLS
CITY_MNTH_SLS
CITY_SUBCAT_SLS
CUSTOMER_SLS
DAY_CTR_SLS
ITEM_EMP_SLS
Revenue [TOT_DOLLAR_SALES] ITEM_MNTH_SLS
MNTH_CATEGORY_SLS
QTR_CATEGORY_SLS
STATE_REGION_MNTH_SLS
STATE_SUBCAT_MNTH_SLS
STATE_SUBCAT_REGION_SLS
SUBCAT_MNTH_CTR_SLS
YR_CATEGORY_SLS
[ORDER_AMT] ORDER_FACT
Discount QTY_SOLD * DISCOUNT ORDER_DETAIL
Notice that the facts you created earlier were saved to this location.
4. In the New Fact - Create New Fact Expression window, for Source table,
select ORDER_DETAIL.
8. Click OK.
9. In the Fact Editor, on the Definition tab, click New and define the two other
fact expressions of Revenue.
13. Following a similar procedure, use the table to create the Discount fact.
Add the following four additional attribute forms to the Customer attribute: First
Name, Address, Email, and Full Name. Full Name should display the last name
and then the first name of a customer (for example, Smith, Jones).
The default report display form should be Full Name. The default browsing
display forms should be Last Name and First Name.
Notice that the attributes you created earlier were saved to this
location.
2. Double-click Customer.
3. In the Attribute Editor, on the Forms tab, select the DESC form and click
Modify.
5. Click OK.
6. On the Forms tab, click New.
7. In the Create New Form Expression window, for Source table, select
LU_Customer.
8. In the Available columns list, double-click Cust_First_Name to add it to
the Form expression window.
9. Under Mapping method, ensure Automatic is selected.
10. Click OK.
11. In the Create New Attribute Form window, under Form general
information, rename the form to First Name.
12. Click OK.
13. Using the following table, follow a similar procedure to create the
remaining three attribute forms: Full Name, Address, and E-mail.
14. After you created the remaining forms, in the Attribute Editor, click the
Display tab.
15. From the Report display forms list, select each form except for Full Name
and click < to return them to the Available forms list.
16. From the Browse forms list, select each form except for Last Name and
First Name and click < to return them to the Available forms list.
How to create an implicit attribute form expression for the Rush Order attribute:
2. In the Create New Form Expression window, for Source table, select
Order_Fact.
5. Click OK.
9. Click OK.
10. In the Create New Attribute Form window, in the Source tables list, check
RUSH_ORDER.
12. When you receive a warning about the data type being text/character
based, click OK.
15. In the Add Children Attributes window, from the Child candidates list,
select Order and click > to add it to the Selected children list.
2. In the Create New Form Expression window, for Source table, select
LU_CUSTOMER.
ApplySimple(datediff(YYYY,#0,Now())",[CUST_BIRTHDATE])
6. Click OK.
9. Click Add.
10. In the Add Children Attributes window, from the Child candidates list,
select Customer and click > to add it to the Selected children list.
9. User Hierarchies
Now that you have created the attributes and specified their parent-child
relationships, you are ready to create user hierarchies. User hierarchies enable
you to easily browse through attributes in Desktop.
Time Hierarchy
- Include all time-related attributes as diagrammed in the logical data
model.
- Make all attributes entry points.
- Allow drilling on the hierarchy.
Customers Hierarchy
- Include all customer-related attributes as diagrammed in the logical
data model. In addition, include the Customer Age and Rush Order
attributes created in section 8 and 9.
- Make all attributes entry points, except Order.
- Lock the Order attribute.
- Allow drilling on the hierarchy.
Geography Hierarchy
- Include all geography-related attributes as diagrammed in the logical
data model.
- Make all attributes entry points.
- Allow drilling on the hierarchy.
Promotions Hierarchy
- Include all promotion-related attributes as diagrammed in the logical
data model.
- Make all attributes entry points.
Products Hierarchy
- Include all product-related attributes as diagrammed in the logical data
model, except Discontinued.
- Make all attributes entry points.
- Allow drilling on the hierarchy.
3. In the Select Attributes window, from the Available objects list, select
Year, Quarter, Month, Month of Year, and Day and click > to add them
to the Selected objects list.
You can use the CTRL or SHIFT key to select multiple attributes at
once.
4. Click OK.
Attributes with a green check mark are entry points. By default, any
attribute without a parent is an entry point.
8. At the bottom of the Hierarchy Editor, leave the Use as a drill hierarchy
check box selected.
10. When notified that this hierarchy has been defined as a drill hierarchy,
click OK.
Purpose: Sales for all items typically peak in December, right around the holiday
season. However, after some further investigation, there were other peak months
in 2005 for certain subcategories. For example, sales for Cameras peaked in April
while those for Art and Architecture peaked in June. In addition, sales for Science
and Technology peaked in March. This report will be used to illustrate how much
sales during the peak months contributed to sales of the same items during the
entire year.
Report Requirements:
Display the revenue for each item in the three selected subcategories
during their peak periods (for example, Cameras in April 2005), as well as
sales of the same items for the entire year.
For each item, show the percent contribution their peak sales contributed
to their annual sales.
Display a totals row that shows a total for each metric by subcategory.
Be sure the percent contribution metric displays Smart Totals. Change the
formatting of these totals to make them stand out.
Report Columns:
Month (not Month of Year)
Subcategory
Item
Seasonal Revenue (Revenue for items in their associated subcategory
during its particular peak month in 2005)
Revenue All Year Revenue (Revenue for items in their associated
subcategory for the entire year)
Percent Contribution of Seasonal to Annual Sales
Purpose: This report will be used to identify the customer cities where the time
between order date and ship date is unacceptably high. A two to three week
delivery period is guaranteed to your customers, so any orders that are shipped
three weeks, or 21 days, past the date the order was placed is considered
delayed.
Report Requirements:
Include all data in the data warehouse with no restriction to a particular
time period.
Display each customer city where items were shipped 21 days or more
later than the day they were ordered.
Display both the number of delayed orders from the customer cities as
well as the total number of orders of those cities. Also, display the percent
of delayed orders to total orders rounded to the nearest whole percent.
Display customer cities grouped by their customer regions.
Include a row showing totals by Customer Region for each metric on the
report. Also include a grand total for all metrics. Be sure the percent metric
displays Smart Totals.
Required Functionality:
Attribute (Creation)
Filters (Attribute-to-attribute expression)
Metrics (Compound)
Metrics (Count)
Metrics (Level)
Number Formatting
Smart Totals
Report Columns:
Customer Region
Customer City
Orders Delayed >= 21 days
Count of All Orders by Customer City
% Late Orders
Purpose: This report will identify all customers who have made more than 20
purchases in 2006. The final report needs to place these customers into quartiles
in each of their customer regions based on the total dollars that they spent.
Report Requirements:
Display Customer Region, Customer Information (including last name, first
name, and address), total dollars spent by each customer, and the quartile
each customer falls into (for example, 1, 2, 3, or 4 with 1 being the 'best'
customers).
Sort the customers alphabetically by Customer Region, then by quartile
within the region (with the best customers appearing first), and finally by
dollar sales within the quartile in descending order.
Include all customer regions, both foreign and domestic.
Prompt the user to select the number of repeat purchases the customer
must have made in order to be included in the report. The user should be
limited to selecting greater than or equal to a number between 15 and
50. (For the initial report, select 20.)
Required Functionality:
Attribute Forms
Metrics (Advanced Functions)
Advanced Sorting
Auto Prompts
Report Columns:
Customer Region
Customer last name, first name, and address
Revenue
Customer Quartile
Promotions Hierarchy
Time Hierarchy
Products Schema
Time Schema
Fact Tables