
Features
| Benefits
| FAQs
|
Features |
Graphical Hierarchy Editor
MicroStrategy Architect provides a visual map of an organization's
database tables and business model. This visual map allows developers
to quickly identify and create relationships among the data elements.
Managers and users can print this visual map for future reference.
View
Graphical Hierarchy Editor
|
|
 |
Schema
Locking
MicroStrategy Architect maintains the integrity of business intelligence
applications by controlling updates to the business model. Schema locking
enables a multi-developer environment with synchronized changes. Locking
the application schema prevents different users from modifying schema objects at the same time as they develop future releases of their
business intelligence applications.
|
|
Freehand SQL-based Logical
Table Creation
Administrators can create logical table views by defining customized table
structures using freeform SQL statements within a MicroStrategy project.
These virtual tables are included in the MicroStrategy metadata and
can be used as derived tables by MicroStrategys ROLAP SQL Engine.
View
Logical Table Editor
|
|
 |
Import PMML Model
MicroStrategy Architect can import and create metrics from Predictive
Modeling Markup Language (PMML) models of sophisticated data mining algorithms.
A PMML Viewer displays detailed information and a graphical representation
of the data mining algorithm. |
|
Import of IBM DB2® Cube
Views
The DB2 Cube View integration utility enables the creation of new MicroStrategy
projects directly from IBM DB2 Cube Views' XML files, drastically shortening
the project creation process. |
|
Automatic Column
Mapping
Using default heuristics, MicroStrategy Architect will identify
the table columns that should normally be mapped together. These
heuristics and mappings can be modified at a later time. Designers
no longer have to manually drag and drop each mapping as in some
competing products; instead, MicroStrategy Architect will perform
all mappings automatically and still allow users to customize
individual mappings as needed.
|
|
Access to Partitioned Fact Tables
Partitioning is a common practice among database administrators,
done to improve data warehouse query performance by splitting
a fact table into several smaller tables according to specific
data ranges. Partitioning by month is very common because monthly
data is unlikely to change. MicroStrategy Architect lets users
define these partitions in the MicroStrategy metadata. By reading
from this metadata,
MicroStrategy Intelligence Server will automatically access the correct
partitioned tables when generating SQL.
|
|