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

OLAP features in Microstrategy

OLAP features in Microstrategy MSTR  OLAP Services uses Intelligent Cube Technology—an in-memory version of report data that can 1 About MicroStrategy OLAP Services  can be manipulated by the MicroStrategy Analytical Engine. MicroStrategy Desktop, Web, and Office users can slice and dice data in reports within Intelligent Cubes without having to re-execute SQL against the data warehouse.  Many of the standard OLAP features that MicroStrategy provides out of the box, such as: Page-by Pivoting Sorting Subtotals Banding Aliasing Outline mode Thresholds etc.. With an OLAP Services license, user can perform additional OLAP analysis, using the following features:  Displaying data on the fly: dynamic aggregation, page  Creating metrics on-the-fly: derived metrics, Defining attribute elements on-the-fly: derived elements,  Filtering data on the fly: view filters and metric filters,  Importing data as an Intelligent Cube
Post a Comment
Read more

Image URL Attribute type HTML Tag in Microstartegy

Creating and attribute with a form with Image URL Image URL Attribute: <img src='images\Folder\UBD\nstudios\N/A.png' height='120' width='163'> <img src='images\Folder\UBD\nstudios\BCU.png' height='120' width='163'> <img src='images\Folder\UBD\nstudios\IUM.png' height='120' width='163'> <img src='images\Folder\UBD\nstudios\WAR.png' height='120' width='163'> <img src='images\Folder\UBD\nstudios\TVN.png' height='120' width='163'> <img src='images\Folder\UBD\nstudios\N/A.png' height='120' width='163'> <IMG src="../images/ 1.png"  height=80 width=400> Concat("../images/Dash/", Id, ".png") ApplySimple(" '<img src=../images/Dash/'+ltrim(str(#0))+'.png height=120 width=120>' ", Id) IF((StudioName = "OURS"), "Ours...
Post a Comment
Read more

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...
Post a 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

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

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 Dashboard performance improvements steps

Microstrategy  Dashboard performance improvements steps: Many times, causes of poor performance can be simplified to specific components. To troubleshoot performance issues, users must identify these components, then make the appropriate modifications to the environment and/or to the MicroStrategy dashboard to reduce bottlenecks. Dashboard execution stages can be represented below: MicroStrategy Intelligence Server When an end user makes a  Document Execution Request  through any client (a web browser via MicroStrategy Web, the MicroStrategy Desktop/Developer client, the MicroStrategy Mobile app, or the MicroStrategy Office client), the request is sent to the MicroStrategy Intelligence Server, which processes the request and prepares the response. The MicroStrategy Intelligence Server will execute all children datasets on the dashboard by either generating SQL and running this against the data warehouse, or by fetching data from a cache. The Inte...
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

Prompt-in-prompt (Nested prompt) feature in a FreeForm SQL Report

Prompt-in-prompt (Nested prompt) feature in a FreeForm SQL Report In some business scenarios, it is required to implement prompt-in-prompt (nested prompt) feature to use the answer of one prompt to qualify on the elements of another prompt in Freefrom SQL reports in MicroStrategy Developer 9.4.x-10.x. The following procedure describes how to achieve prompt-in-prompt in a Freeform SQL report in MicroStrategy Tutorial project: Create a new filter, select Add an Attribute qualification and choose the highest level attribute Country. Make sure to Qualify On: Elements. Click Prompt as the image shown below. Accept all the default values without any changes in the popped up window after clicking on "Prompt" as shown below. Save the filter as "Country Filter". Click "Prompt", choose "Use a filter to reduce the number of elements" option and select Country Filter created in last step, as shown below. Save the filter as "Region Filter...
1 comment
Read more