A data mart is a data organization that is based on a business category. You can use data marts to organize data for a specific product or scenario. In most cases, a data mart belongs to an application layer and depends on the aggregate data in one or more common layers. This topic describes how to create a data mart and manage subject areas that are associated with a data mart.
Prerequisites
A business category is created to differentiate business data based on specific scenarios. For more information, see Business category.
Background information
A data mart defines business subjects for a business category. You can categorize data in a data mart into different subject areas based on various analysis perspectives. Data marts are used to collect statistics on business applications and analyze the statistics. For example, you can create a data mart to collect statistics on an operations platform and analyze the statistics.
Create a data mart
Go to the Data Mart page.
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose . On the page that appears, select the desired workspace from the drop-down list and click Go to Data Modeling.
In the top navigation bar of the Data Modeling page, click Data Warehouse Planning. The Data Layer page appears.
In the left-side navigation pane of the Data Warehouse Planning tab, choose to go to the Data Mart page.
Create a data mart.
On the Data Mart page, move the pointer over the
icon and select Create First-level Data Mart. In the Create First-level Data Mart dialog box, configure the parameters.
Parameter
Description
Abbreviation
The abbreviation for the name of the data mart.
The abbreviation can be up to 128 characters in length. It can contain lowercase letters, digits, and underscores (_) and must start with a lowercase letter.
Mart Name
The name of the data mart.
The name can be up to 2,048 characters in length. It can contain letters, digits, underscores (_), ampersands (&), and parentheses () and must start with a letter or digit.
Mart Type
The type of the data mart. Valid values:
Business Mart: a type of data mart that is oriented to business requirements.
Data Application Mart: a type of data mart that is oriented to requirements for data products.
Common Mart: a type of data mart that can be used for general purposes at application layers.
Business Category
The business category to which the data mart belongs. For more information about business categories, see Business category.
Owner
The owner of the data mart. The default value is the current logon account.
Description
The description of the data mart.
The description of the data layer can be a maximum of 2,048 characters in length.
Click OK. The data mart is created.
If you want to modify or delete a data mart, you can find the name of the data mart in the left-side navigation tree of the Data Mart page, right-click the name, and then select Edit or Delete.
NoteBefore you delete a data mart, you must remove all association relationships of the data mart.
Manage subject areas associated with a data mart
A subject area is a collection of business subjects and is used to categorize data in a data mart from various analysis perspectives. You can view the subject areas that are associated with a data mart in the Subject Area Management section of the details page of the data mart. You can also modify or delete the association relationship between a subject area and the data mart based on your business requirements.
If you click Delete in the Actions column to delete the association relationship between a subject area and the data mart, the subject area is also deleted. Proceed with caution.
Create a child data mart
You can create child data marts for each data mart. The method used to create a child data mart is the same as the method used to create a data mart.
What to do next
After a data mart is created, you can associate the data mart with an application table when you create the application table for business analysis. For information about how to create an application table, see Create a logical model: application table.