Share

Página Principal > Software > Development Tools: Architect > MicroStrategy Architect Product Features

MicroStrategy Architect™

Features | Benefits | FAQs

MicroStrategy Architect Product Features

Interactive Architect Interface

MicroStrategy Architect provides a single consolidated view of the organization’s database tables and business model. Seeing the two side by side enables application developers to quickly create new project objects. The interactive interface allows them to right click directly on the objects, drag-and-drop, and format them in the same interface. Hierarchy editing also uses these tools to easily create all the relationships users need from the database objects.


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 Views

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 MicroStrategy’s ROLAP SQL Engine.


Automated Project Modeling

Using advanced recognition algorithms, MicroStrategy Architect can automatically identify facts and attributes from database table columns based on flexible parameters, saving developers time and effort. This feature can also map attributes to columns from different tables that provide the same information, allowing for as many sources as possible.


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.