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

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

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 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

Using Scan MD Microstrategy

ScanMD  WHAT IS SCAN MD? ScanMD is a troubleshooting application whose aim is to provide a  quick resolution  to  known  metadata logical inconsistencies.  Logical inconsistencies are errors within an object's definition structure. The word 'known" means that those erroneous structures have already been investigated and processed by MicroStrategy Technical Support and, as a result, a Test has been implemented in ScanMD.  It is  not  the intention that ScanMD be used as a proactive method for addressing metadata inconsistencies.  If you find yourself proactively running ScanMD and/or finding inconsistencies through ScanMD then please contact MicroStrategy Technical Support as this means that there is, most likely, a deeper problem to be investigated. Refer to the following technical note if ScanMD is going to be executed against a 10.3 and higher metadata: CONSIDERATIONS/GUIDELINES ScanMD is to be us...
2 comments
Read more

Email Subscription in Microstrategy

Create Email Subscription in Microstrategy Creates an email subscription. Do not include any leading or trailing spaces in the ANSWER parameters. This causes a SQL error and prevents the command from executing. Ex: CREATE EMAILSUBSCRIPTION "New Multi Users" FOR OWNER "administrator" SCHEDULE "Books Closed" CONTACTGROUP "TEST"  CONTENT "Electronics Revenue by Region" IN FOLDER "\Public Objects\REPORTS\SUBJECT Areas\Sales and Profitability Analysis" IN PROJECT "MicroStrategy Tutorial" DELIVERYFORMAT HTML  EXPIRATIONDATE NEVER EXPRIED FILENAME "file_name"   SUBJECT  "Test REPORT" MESSAGE "Please Test"; CREATE EMAILSUBSCRIPTION [ subscription_name ] [FOR OWNER login_name ] SCHEDULE schedule_name  (ADDRESS address_name | USER user_name  | CONTACT contact_name [ADDRESS contact_ address_name ] | CONTACTGROUP contact_group_name ) CONTENT ( report_or_document_name IN FOLDER   loc...
1 comment
Read more

Export a Report Services document to Excel with formatting using URL API

Export a Report Services document to Excel with formatting using URL API in MSTR Web In order to export a document in excel format using the URL API, the executionMode must be set to 4.  If excutionMode is not provided in the URL, by default PDF will be used as executionMode.   Below are the list of parameters that the URL must contain in order to execute correctly.   evt= 3069 src= Main.aspx.3069 executionMode= 4 documentID= 7E1644CA424F482DA811569FCE8127FF( Replace the document Id with your document ID)   Sample URL for .NET environment: http://WebServerName/MicroStrategy/asp/Main.aspx?evt=3069&src=Main.aspx. 3069 &executionMode= 4 &documentID= 7E1644CA424F482DA811569FCE8127FF    
1 comment
Read more

Microstrategy Document Autotext macros:

Autotext  code/macros in  Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add  document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard:  AUTOTEXT DESCRIPTION   {&PAGE}  Display the current page.  {&NPAGES}  Display the total number of pages.  {&DATETIME}  Display the current date and time.  {&USER}  Display the user name that is executing the Report Services Document.  {&DOCUMENT}  Display the document name.  {&DOCUMENTID}  Display the document ID.  {&DESCRIPTION}  Display the document description.  {&PROJECT}  Display the project name.  {&EXECUTIONTIME}  Dis...
2 comments
Read more

Microstrategy Alerts setup

Alerts Editor Alerts can be sent to an email address or to an iPhone, iPad, or Android device with MicroStrategy Mobile. This allows users to be notified of data that is likely to be important for making business decisions. You can also have formatting automatically applied to metric values in the report, to draw immediate attention to the data that meets the alert's threshold conditions. For example, when the Inventory Count data in a report falls below 1,000 units, you can have the report sent to you, with the values below 1,000 displayed in red text. You can specify a subject and message to display for the alert, as well as a report or document to be displayed when viewing the alert, as described below. You can receive and view alerts on a mobile device even if the MicroStrategy Mobile application is not running. Prerequisites    You must have the MicroStrategy Distribution Services product installed and MicroStrategy Web must be configured to use Distribu...
Post a Comment
Read more

Fact tables levels tables in Microstrategy explained

Fact tables levels in Microstrategy: Fact tables are used to store fact data. Fact tables should contain attribute Id's and fact values which are measurable. All the descriptive information about the fact tables should stored in Dimension tables either in Star Schema fashion or Snow Flake Schema fashion which is best suited to your reporting solution. Since attributes provide context for fact values, both fact columns and attribute ID columns are included in fact tables. Facts help to link indirectly related attributes using these attribute ID columns. The attribute ID columns included in a fact table represent the level at which the facts in that table are stored. So the level of a fact table in the Fact_Item_Day_Customer can be the attribute Id's which is at Day, Item & Customer Id level. For example, fact tables containing sales and inventory data look like the tables shown in the following diagram: Base fact columns ver...
2 comments
Read more