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 URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...
2 comments
Read more

Create an alert-based subscription in MicroStrategy Distribution Services

Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief  steps bel...
3 comments
Read more

Non Aggregate metrics Beginning lookup, Ending lookup, Beginning fact., Ending fact

Non Aggregate metrics  Beginning lookup,  Ending lookup,  Beginning fact .,  Ending fact A nonaggregatable metric, such as an inventory metric, is one that should not be aggregated across an attribute.   For example, if you have monthly inventory numbers in your data warehouse and want to calculate the yearly inventory, adding the monthly numbers together does not provide a useful business measure. Instead, you may want to use the end-on-hand and beginning-on-hand inventory numbers to see how the total inventory changed during the year.  The following options are available: • To use the first value in the lookup table, select  Beginning lookup . • To use the last value in the lookup table, select  Ending lookup . • To use the first value in the fact table, select  Beginning fact . • To use the last value in the fact table, select  Ending fact .
Post a Comment
Read more

"System Prompt" and its uses in MicroStrategy

System Prompt and its uses in MicroStrategy WHAT IS A "SYSTEM PROMPT"? "System Prompt" is a system object that was introduced back in version 8.0.0. The object is named as "User Login" and is implemented as a prompt object. The object can be found under Public Objects > Prompts > System prompts, as shown below: Unlike ordinary prompt objects, system prompts don't require any answers from the user. When a report containing a system prompt runs, the prompt is answered automatically with the login of the user who runs the report. On the other hand, like other prompt objects, answers to system prompts are used to match caches. Therefore, users don't share caches for reports that contain system prompts. For details on how caches are matched, refer to the following MicroStrategy Knowledge Base document: KB5300-7X0-0147 - How are caches matched in MicroStrategy Intelligence Server 7.x? WHEN ARE SYSTEM PROMPTS USED?    System pr...
Post a Comment
Read more

Microstrategy Dossiers explained

Microstrategy  Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has  evolved dashboards to the point that they are more than dashboards - they are  interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so  the've  renamed VI dashboards to  ‘ dossiers ’.  Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers   With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...
7 comments
Read more

Bursting file subscriptions Microstartegy

Bursting file subscriptions: Delivering  parts of reports across multiple files: Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis). Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region. As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Ele...
1 comment
Read more

Control the display of null and zero metric values

Show   Control the display of null and zero metric values in a grid report You can determine how to display or hide rows and columns in a grid report that consist only of null or zero metric values. You can have MicroStrategy hide the rows and columns in the following ways: Hide rows and columns that consist only of null metric values Hide rows and columns that consist only of zero metric values Hide rows and columns that consist only of null or zero metric values (default) Once you have defined how MicroStrategy hides null and zero metric values in the grid, you can quickly show or hide the grid using the Hide Nulls/Zeros option in the Data menu, as described below, or by clicking the  Hide Nulls/Zeros  icon  in the Data toolbar. To determine how null and zero metric values are displayed or hidden in a grid report Open the report in Edit mode. From the  Tools  menu, select  Report Options . The Report Options...
Post a Comment
Read more

Retrieve a list of user groups and the associated users in MicroStrategy Developer 9.x / 10.x

Retrieve a list of user groups and the associated users in MicroStrategy Developer Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9.x, select 'Project Documentation' from the Tools menu to start the wizard. Select any project that is in the project source that contains the users and groups and click Next. Select only Configuration Objects for documentation. Uncheck the 'Basic Properties' object category from the next screen, as shown below: Then select only 'User Group' under the Configuration Objects section and only 'Groups' and 'Members' under the Definition section, as shown below: Go through the rest of the wizard, and open the resulting documentation. After navigating down to the User Groups, the documentation should look similar to the following image: This page shows every group, any child groups, and all members of each group.
Post a Comment
Read more

Relationship with Report Filter options for Levels metrics

Relationship with Report Filter options for Levels metrics You can define how the report filter affects the metric calculation. From the  Relationship with Report Filter  drop-down list, select one of the following: • To include only data that meets the conditions in the report filter in the metric calculation, select  Standard filtering . • To raise the level of the report filter to the level of the target, if possible, then apply the report filter to the metric calculation, select  Absolute filtering . For example, the report filter contains the Washington, DC, Boston, and New York call centers, but the Revenue metric is calculated at the Region level. Because Call Center is a child attribute of Region, the report filter's level is raised to the Region level, and the report filter is treated as if it includes the regions that contain Washington, DC, Boston, and New York (in this case, Mid-Atlantic and Northeast). Data from all call centers in the Mid-At...
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