KB30106: How does automatic column recognition work in MicroStrategy Architect 9.x?

Architect 9.x can automatically create attributes and facts in order to save time during the schema creation process. The facts and attributes are created based on data types, database column names, primary and foreign keys, and other schema creation heuristics.
 
The user can define how attributes and facts are created when tables are added to the project by defining the automatic column recognition rules available in the Strategy Architect Settings menu, by following the steps below:
 

1. Open the Setting menu, located under Options:

 
     
 
 
 
 
 
 
 
2.   Go to the Column Recognition tab:
 

• Do not use auto recognize: This option is used to  disable the automatic creation of attributes and facts when tables are added to the project using Architect.
• Use auto recognize: This option is used to enable the automatic creation of attributes and facts when tables are added to the project using Architect. These are created based on the following schema creation heuristics and rules:
  
• Separator: The character used as a separator in the database column names. For instance, a database column name such as USER_ID uses the undersocre character (_) as a separator.
• Attribute naming rule: Database column name suffixes that identify that the columns should be mapped to a new attribute as the identity form. A semicolon (;) can be used to separate suffixes that are to be mapped to new attributes. It is also possible to define how the attribute name is created by using a vertical bar (|) to define what the suffix is replaced with in the resulting attribute name.
• Attribute form naming rule: Database column name suffixes that identify that the columns should be mapped to a new attribute form.
• In addition to using these rules to define attributes and attribute forms, selecting the Use auto recognize option also employs other schema creation heuristics:
  
• The automatic column mapping rules described in Automatically column recognition are employed to map columns to existing attribute forms that use the columns in their definitions.
• An attribute is created for any column defined as a primary or foreign key, and the column name for the primary key is used to define the attribute name. The column name for the primary key is used to define the attribute name even if the primary key column is not included in the project.
• Every column must be mapped to either a fact or an attribute. If none of the schema creation heuristics or the rules you define can determine whether to create a fact or attribute for the column, an attribute is created for the column.

In addition, even when the option to not use auto recognize is selected, it is still possible to take advantage of the auto recognize feature on a table by table basis by following the steps below:

1. Right click on the table in the Architect Project Tables View.
2. Select Recognize > Attributes, Facts, or Both, as shown in the screenshot below: