Loading Intelligent Cubes when Intelligence Server Starts

When Intelligence Server is started there are various tasks that are processed to prepare a reporting environment. You can include loading all published Intelligent Cubes as one of the tasks completed when Intelligence Server is started. This affects when the load time required for Intelligent Cubes occurs.

Below are the steps to enable or disable loading Intelligent Cubes when Intelligence Server starts

In Developer, log in to a project with a user account with administrative privileges.
Right-click the project and select Project Configuration.
Expand Intelligent Cubes, and then select General.
Select or clear the Load Intelligent cubes on startup check box to enable or disable loading Intelligent Cubes when Intelligence Server starts.
Click OK.

It is always useful to consider whether to load Intelligent Cubes at Intelligence Server startup or when a report is executed that accesses a published Intelligent Cube are described in the table below:

Method	Pros	Cons
Loading Intelligent Cubes when Intelligence Server starts	Report runtime performance for reports accessing Intelligent Cubes is optimized since the Intelligent Cube for the report has already been loaded. This practice is a good option if Intelligent Cubes are commonly used in a project.	The overhead experienced during Intelligence Server startup is increased due to the processing of loading Intelligent Cubes. All Intelligent Cubes for a project are loaded into Intelligence Server memory, regardless of whether they are used by reports or not.
Loading Intelligent Cubes when a report is executed that accesses a published Intelligent Cube	The overhead experienced during Intelligence Server startup is decreased as compared to including loading Intelligent Cubes as part of the startup tasks. If Intelligent Cubes are not required by any reports, then they do not need to be loaded into Intelligence Server and no overhead is experienced. This practice is a good option if Intelligent Cubes are supported for a project, but some of the Intelligent Cubes are rarely used in the project.	Report runtime performance for reports accessing Intelligent Cubes can be negatively affected as the Intelligent Cube must first be loaded into Intelligence Server. You can also load Intelligent Cubes manually or with subscriptions after Intelligence Server is started.

The procedure below describes how to enable or disable loading Intelligent Cubes when Intelligence Server starts.

The act of loading an Intelligent Cube can require memory resources in the area of two times greater than the size of an Intelligent Cube. This can affect performance of your Intelligence Server as well as the ability to load the Intelligent Cube.

Comments

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select Custom as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the Project Design Guide . ...

No 'Alert' option appear when trying to create an alert-based subscription in MicroStrategy Distribution Services

The 'Alert' option does not appear when attempting to create an alert-based subscription in MicroStrategy Distribution Services In MicroStrategy Distribution Service 9.x and 10.x, and 11.x versions it is possible to create an alert-based subscription. When right-clicking the metric header of a report in MicroStrategy Web 9.0.x, the 'Alerts' option does not appear: Cause : This issue occurs because the user attempting to create the alert does not have all of the necessary privileges on alerts. Fix : In order to create an alert-based subscription, the following privileges are required: In order ti get permissions to create alerts the user should be given the following privileges by the admin: New Version of Microstrategy 11.x: Server- Distribution: Older Versions of Microstrategy 9.x, 10.x etc..: Web Reporter > Web user Web Analyst > Web create alert ...

Differences between OLAP cubes and Super cubes

Differences between OLAP cubes and Super cubes OLAP Super Version Existed before MicroStrategy 10.0 New in MicroStrategy 10.0 Data Volume In 9.x, limited to 2 billion rows Each partition can have up to 2 billion rows ...

Reduce Intelligent Cube Size By Finding Intelligent Cube Objects Which Are Not In Use

Reduce Intelligent Cube Size By Finding Intelligent Cube Objects Which Are Not In Use If the i-cubes can potentially be reduced in size an audit can be performed on the cube objects to see which cube objects are not being used by any of the view reports, documents, or dossiers. The below are examples for a few of the common metadata database platforms . NOTE: To perform this audit, queries are run against the MicroStrategy metadata database. Ensure a metadata backup is taken prior to performing the below actions. Steps: 1) Identify the object ID of the Intelligent cube to be audited by checking the objects Property window 2) Identify the object ID of the project this cube exists within by opening the Project Configuration Sample Cube ID = CFAF1E9B4D53990698C42E87C7AF2EB5 Sample Project ID = B7CA92F04B9FAE8D941C3E9B7E0CD754 3) Run the below SQL against the metadata database by replacing the Cube ID and Project ID within the respective ...

Compound key attribute

Compound key attribute A compound key attribute is an attribute whose primary key is made up by the combination of two or more columns. The multiple columns are joined with other attributes, typically in a many-to-many relationship . To create a compound key, users must create multiple attribute forms, group them together and set the form group as the key for the attribute. Use the same steps as specified in the help menu: Open attribute editor (right-click on attribute and select 'Edit') Select the forms that will make up the compound key From the 'Edit' menu, choose 'Group' NOTE: Modifying the key form will trigger required updates when saving. This may make related application objects (reports, filters and metrics) unusable. Click on 'Yes' to continue, when prompted, in a dialog box, to confirm this action Save the changes. Choose 'Update Schema' from the Schema menu

Algorithm to calculate Logical Table Size in Microstrategy

How are the fact tables determined using the logical table size for SQL generation in MicroStrategy The logical table size is an integer number that represents the granularity or level of aggregation of a particular table. It is called 'logical' because it is not related to the physical size of the tables (number of rows). It is calculated according to the attribute IDs that are present in the table and their level in the system hierarchy. Even though, the number does not reveal the actual number of rows in the table, it is an accurate way of measuring a table size without having to access its contents. IMPORTANT: The system hierarchy is defined by the parent-child relationships between attributes of the same family (formerly known as a dimension), not by user-defined hierarchies (i.e., drilling hierarchies). MicroStrategy Engine utilizes an algorithm based on attribute keys to calculate the Logical Table Size (LTS): Given the following tables: ...

Microstrategy Removing sections that do not have metric data

Removing sections that do not have metric data This is an interesting feature which might not be explored by many of us and it comes us handy. A cross join between datasets can result in rows or Group Header/Footer sections that do not have metric data. For example, a document contains two datasets. Dataset 1 contains Year and Revenue, with data for three years (2007-2009). Dataset 2 contains Year and Profit, filtered to return data for only two years (2008 and 2009). If you place Year and Profit in the Details and execute the document, it displays three rows, although no profit data exists for 2007. This is a product of the cross join between the two datasets. You do not want to see the blank line for 2007 since it does not give you any data for profit. You can select the Trim sections for which no metric value data is available check box. This removes the row for 2007, since no metric data for Profit is available for 2007. The results are shown below: ...

Create a transaction services photo uploader

Create a transaction services photo uploader 1. Create a new table "photo_upload" in Tutorial warehouse database (the default location: C:\Program Files\MicroStrategy\Tutorial Reporting\TUTORIAL_DATA_7200.mdb), as shown below: 2. The 'photo_upload' table has to be pre-populated with *exactly* 10 rows of data, the values for the 'ID' column should be 1-10 and the values for the 'uploaded' column should all be 0 3. In MicroStrategy Desktop, create a freeform report "R1" based on the new table "photo_upload" in Tutorial data created at step 1, as shown below: SELECT Location, Description, ID, uploaded, numbers FROM PHOTO_UPLOAD 4. Create another table for transaction insert SQL. Make sure to create an 'autonumber' type ID as primary key for this table, or auto_increment ID for different DBs. 5. Create...

Conversion failed when converting the varchar value 'xxxx' Microstartegy

Error "Conversion failed Error "Conversion failed when converting the varchar value 'xxxx' to data type int" happens when displaying Picture type attribute form using ApplySimple in expression against SQL Server 2012 in MicroStrategy The attribute form is in Picture type and defined with the following ApplySimple function with Int type column [ID_BARANG] as the input parameter against SQL Server 2012. Solutions is to use Concat("Images/demo/s", [BARANG_ID_INT], ".png") ApplySimple("'images/demo/'&#0&'.png'", [ID_BARANG]) However, when running reports with attribute to show the picture form in Web, error message happens in both Web and Developer. Conversion failed when converting the varchar value 'images/demo/s' to data type int. STEPS TO REPRODUCE: SQL Server 2012 database should be used as the warehouse. Create an attribute form as type Picture and us custom expressi...

Predictive modelling in Data Science using Microstrategy

Creating a predictive modelling in MicroStrategy MicroStrategy Data Mining Services has been evolving to include more data mining algorithms and functionality. One key feature is MicroStrategy Developer’s Training Metric Wizard. The Training Metric Wizard can be used to create several different types of predictive models including linear and exponential regression, logistic regression, decision tree, cluster, time series, and association rules. Linear and exponential regression The linear regression data mining technique should be familiar to you if you have ever tried to extrapolate or interpolate data, tried to find the line that best fits a series of data points, or used Microsoft Excel’s LINEST or LOGEST functions. Regression analyzes the relationship between several predictive inputs, or independent variables, and a dependent variable that is to be predicted. Regression finds the line that best fits the data, with a minimum of error. For example, you have a dataset ...

Microstrategy Analytics

Search This Blog