Skip to main content

Microstrategy Release Types



Platform release

  • Interval: Annually every twelve (12) months in December
  • Who: Entire customer base
  • What: Focus on production level security, stability, and performance defect fixes for all customers.
  • Expectation: Customer has chosen platform path and wants product stability without new enhancements.
  • Support: Three (3) years, patches for approved P1 defects, and regular hotfix cadence addresses critical defects.

Feature Release

  • Interval: Quarterly every three (3) months
  • Who: Customers with specific feature requirements.
  • What: New functionality developed in close collaboration with customers and customer council.
  • Expectation: Customer has chosen feature path, will consume further feature releases.
  • Support: Six (6) months patch support for approved P1 defects and (eighteen) 18 months troubleshooting. Customers upgrade to next feature release for roll-up fixes.
Why has MicroStrategy introduced “Platform” and “Feature” releases?
MicroStrategy moved to a quarterly release cadence when MicroStrategy 10 was released in June 2015. This pro-active change has enabled us to provide innovative improvements, feature enhancements, and quick-fixes in a more rapid and agile fashion to better support you, our valued customer. The shortened release cycle has made it easier to address your needs more quickly. We do understand that it can be challenging for some customers to keep up with this prompt pace and determine when the best time to upgrade to a newer version of MicroStrategy for their enterprise.
What is a "Platform" release?
MicroStrategy considers a “platform” release one that is well-suited for broad-based customer adoption. We anticipate platform releases will be delivered approximately every 18 months and will be supported for a total of 36 months. We will make regular stability patches and hotfixes to a platform release, but no new features or functionality will be added to this specific version.
What is a "Feature" release?
We expect feature releases to be delivered every three months and will be supported for a total of six months**. Feature releases will include new features and functionalities, as well as patches and hotfixes from the most recent platform release. This type of release is designed for specific feature requirements for those customers who want to gain access to the latest features and functionality, and are willing to embrace the added commitment of frequent upgrades. For example, MicroStrategy version 10.4 is a platform release, and customers can expect versions 10.5, 10.6, etc. to be feature releases until our next platform release is delivered.
If I am currently using a “Feature” release, will I really be unsupported within six months if I do not upgrade?
Customers on outdated “Feature” releases will still be able to access support via all of the normal support channels as long as their entitlement is active. MicroStrategy will also continue to provide patches for approved P1 defects such as security issues or crashes during the six-month support window. Lower priority items will be included in future versions and customers will be expected to upgrade to the next version so that lower priority issues are successfully resolved.
Once I begin using a “Feature” release, will I be required to upgrade to the newest “Feature” release in order to obtain fixes?
Yes, that is the main distinction between the “platform” and “feature” releases. As feature releases are released every three months. This version will include all fixes and patches in addition to some new features. Therefore, MicroStrategy will not issue hotfixes for feature releases. Hotfixes will only be issued on platform releases.
Can I use a feature release and platform release in parallel?
Yes! If you would like to test out a feature release you are more than welcome to download and install the latest release. This can help speed the UAT process or enable you to give specific features to a sub-set of users without upgrading your entire environment.

Expected Expiration Dates for Existing Versions

VERSION
SUPPORT STATUS
ORIGINAL RELEASE DATE
EXPECTED EXPIRATION DATE *
2019SupportedDecember 13, 2018December 31, 2021
11.0SupportedSeptember 25, 2018March 31, 2019
10.11xSupportedMarch 30, 2018September 30, 2019
10.10xSupportedDecember 5, 2017June 30, 2019
10.9xSupportedSeptember 27, 2017March 31, 2019
10.8xExpiredJune 29, 2017December 31, 2018
10.7xExpiredMarch 23, 2017September 30, 2017
10.6xExpiredDecember 16, 2016June 30, 2017
10.5xExpiredSeptember 14, 2016March 31, 2017
10.4xSupportedJune 15, 2016December 31, 2020
10.3xSupportedMarch 15, 2016March 31, 2019
10.2xExpiredDecember 18, 2015December 31, 2018
10.1xExpiredAugust 31, 2015August 31, 2018
10.0xExpiredMay 29, 2015May 31, 2018
9.5xExpiredJanuary 22, 2015December 31, 2018
9.4xSupportedSeptember 30, 2013June 30, 2019
9.3xExpiredSeptember 13, 2012April 1, 2016
9.2xExpiredMarch 30, 2011April 1, 2015
9.0xExpiredMarch 20, 2009October 1, 2013
8.1xExpiredMarch 23, 2007September 1, 2011
8.0xExpiredFebruary 1, 2005April 2, 2009
7.5xExpiredNovember 18, 2003November 20, 2006
7.3xExpiredNovember 21, 2002July 15, 2005
7.2xExpiredApril 6, 2002July 15, 2005
7.1xExpiredMarch 31, 2001March 1, 2004
7.0xExpiredSeptember 12, 2000March 1, 2004
Labels:

Comments

Post a Comment

Popular posts from this blog

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 . ...
4 comments
Read more

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: ...
Post a Comment
Read more

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 ...
Post a Comment
Read more

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
Post a Comment
Read more

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: ...
Post a Comment
Read more

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 ...
1 comment
Read more

Scheduling a report or document to be sent to an FTP in MSTR

Scheduling a report or document to be sent to an FTP server You can have a report or document automatically delivered to a location on your FTP server on a specific schedule. To do so, you must subscribe to the report or document, as described in the steps below. You can customize your subscription by typing macros in the  File Name ,  Sub-folder , or  Zip File Name  fields. These macros are automatically replaced with the appropriate text when the report or document is delivered. For example, you create a subscription to a document. If you type  {&Project}  in the  File Name field, the name of the project in which the document is saved is displayed in the name of the document when it is delivered. • This procedure assumes that an administrator has already added your FTP server as a new device in Developer. Steps to do so are included in the  System Administrator Help . To send a report or document to an FTP server on a schedule ...
Post a Comment
Read more

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...
1 comment
Read more

Enable Incremental fetch in MSTR documents

Enable Incremental fetch in MSTR documents Incremental fetch divides large documents or layouts into pages, thereby loading the data in batches (or blocks) rather than all at the same time. This improves the usability and performance of a large document or layout, by reducing the load and overall memory usage on the web server. To apply incremental fetch to a document In MicroStrategy Web, open the document in the Document Editor. If the document contains multiple layouts, select the layout to apply incremental fetch to. From the  Tools  menu, choose  Document Properties . The Document Properties dialog box opens. On the left, under Layout Properties, select  Advanced . Select the  Enable Incremental Fetch  check box. From the  Fetch Level  drop-down list, select the object to be counted for the incremental fetch level. If the document or layout is grouped, the groups are displayed in the drop-down list. Groups that are displayed...
1 comment
Read more