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

Microstrategy "Error type: Odbc error. Odbc operation attempted

 "Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’.  Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...
4 comments
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

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in  Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to  create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...
3 comments
Read more

mstrio – Python and R wrappers for the MicroStrategy

mstrio – Python and R wrappers for the MicroStrategy REST APIs Connecting to MicroStrategy  Create a connection to the Intelligence Server using   Connection()   and    connect()  in Python and R, respectively. Required arguments for the   Connection()  function are the URL for the MicroStrategy REST API server, MicroStrategy Intelligence Server username and password, as well as the MicroStrategy project name. By default, the   connect()  function anticipates your MicroStrategy Intelligence Server username and password. LDAP authentication is also supported. Use the optional argument    login_mode=16    in the    connect()  function for LDAP authentication.  Extract data from cubes and reports  To extract data from MicroStrategy cubes and reports, use the   get_cube()  and   get_report()  functions. Use...
8 comments
Read more

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A  cache is a result set that is stored on a system to improve response time in future requests.  With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the  Administration  menu, point to  Projects , and then select  Project Configuration . The Project Configuration Editor opens. 3 Expand  Caching , expand  Auxiliary Caches , then select  Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the  Administration  menu in Developer, point to  Server , and then select  Purge Server Object Caches . 4 Click  Purge Now . To purge web cache follow the steps in the link ...
3 comments
Read more

MicroStrategy VLDB properties with Hive

 Recommended VLDB Properties for use of  MicroStrategy 9 with Hive 0.7x The recommended VLDB optimizations for Hive 0.7x are listed below. These values are set by default when the "Hive 0.7x" database object is used (set at  Configuration Managers > Database Instances > Database Instance > Database connection type ) Selected Default VLDB Properties for Hive 0.7x  VLDB Category  VLDB Property Setting  Value   Tables  Fallback Table Type  Permanent Table  Tables  Maximum SQL Passes Before FallBack   0 (no threshold)  Tables  Maximum Tables in FROM Clause Before FallBack  0 (no threshold)  Tables  Drop Temp Table Method  Drop after final pass   Tables  Table Creation Type  Implicit Table  Query Optimizations   Sub Query Type   Use Temporary Table, falling back to IN (SELECT COL) for cor...
Post a Comment
Read more

Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy

Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy MicroStrategy has introduced a feature known as, Incremental Refresh Options, which allow Intelligent Cubes to be updated based on one or more attributes, by setting up incremental refresh settings to update the Intelligent Cube with only new data. This can reduce the time and system resources necessary to update the Intelligent Cube periodically versus a full republish. For example, if a user has an Intelligent Cube that contains weekly sales data, the user may want this Intelligent Cube to be updated at the end of every week with the sales data for that week. By setting up incremental refresh settings, he can make it so that only data for one week is added to the Intelligent Cube, without affecting the existing data and without having to reload all existing data. Users can select t...
7 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...
2 comments
Read more

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...
3 comments
Read more