MicroStrategy project

A project is where you build and store all schema objects and information you need to create application objects such as reports in the MicroStrategy environment, which together provide a flexible reporting environment. A project also represents the intersection of a data source, metadata repository, and user community. In MicroStrategy Developer, projects appear one level below project sources in the Folder List.

A project:

Determines the set of data warehouse tables to be used, and therefore the set of data available to be analyzed.
Contains all schema objects used to interpret the data in those tables. Schema objects include facts, attributes, hierarchies, and so on. Schema objects are discussed in later chapters in this guide.
Contains all reporting objects used to create reports and analyze the data. Reporting objects include metrics, filters, reports, and so on. Report objects are covered in the Basic Reporting Guideand the Advanced Reporting Guide.
Defines the security scheme for the user community that accesses these objects. Security objects include security filters, security roles, privileges, access control, and so on. Security and other project-level administrative features are discussed in the System Administration Guide.

A project can contain any number of reports in addition to a number of other objects that support simple and advanced reporting requirements. Conceptually, a project is the environment in which all related reporting is done. A project can contain many types of objects, including application objects such as filters, prompts, metrics, and reports that you can create using schema objects such as attributes and facts.

Projects are often used to separate data from a data warehouse into smaller sections of related data that fit user requirements. For example, you may have a project source separated into four different projects with analysis areas such as human resources, sales distribution, inventory, and customer satisfaction. This allows all of your users in the human resources department to use the human resources project and they do not have to look through inventory data that they are not interested in.

Some key concepts to understand before you begin creating a project are as follows:

A project is created within a specified metadata repository, determined by the project source through which you create the project.
The project’s warehouse location is specified by associating it with the appropriate database instance.

The procedures associated with these concepts are explained in Creating a production project.