Bryan's BI Blog pushing what's possible

15

MicroStrategy TaskProc Enhancement in 9.2 SDK

One thing that you’ll notice when trying to use the TaskProc as a method of feeding MicroStrategy data into an external application is that the various options for results are none too friendly.  The XML options are all very bloated with metadata/formatting overhead and the other delivery packages are just wrappers for the XML, so they make it worse.  The handy ReportViewer style that can...

3

Improving Query Flexibility with Partition Mapping

Partition Mapping is a traditional database concept that MicroStrategy has adopted in the SQL Engine to give you even more options for performance and tuning.  Traditional Database Partitioning involves taking a large table and breaking it up into smaller pieces by separating it at logical break points, such as one table per year or per region.  The database would then be intelligent enough to know...

50

Incremental Refresh of Intelligent Cubes

Arguably, the headliner feature of MicroStrategy 9 was the introduction of Intelligent Cubes.  This powerful feature revolutionized project speed and design by allowing for lightning fast data access directly from memory.  After implementation, it gives the developer the best of both ROLAP and MOLAP worlds without either of the draw backs.  You get the speed of MOLAP data requests, but the flexibility of ROLAP ad-hoc analysis. With...

19

Tracking Table Usage with Enterprise Manager

Capping off this week of Aggregate Table talk, one piece of insight you’ll definitely want to have is which tables are being used by which reports.  Sometimes it can be handy to know if a particular table is no longer needed and can be discarded, or to identify reports that are hitting detail tables instead of aggregates.  MicroStrategy Enterprise Manager comes with lots of statistical...

17

Fact and Attribute Anchoring

Carrying on with this week’s theme of Aggregate tables is an exploration of a concept I call Anchoring.  As your data volume grows and reporting complexity increases, an inevitable outcome is the growth of complex Aggregate and Sub-Set tables.  While as Architects we are effectively teaching MicroStrategy the “best” way to write a query by laying out rules such as key tables and parent/child relationships,...

4

Handling Count Metrics For Aggregates

Here’s a quick tip for a scenario that I encountered in a project today.  Say that you’ve got a schema where one of the metrics will be a Count(*) from the Fact Table.  This is a common occurrence when the Fact Table contains Events that may or may not have traditional facts, such as Revenue/Cost, but also the existence of the record is a fact itself. For...

16

Aggregate Tables

Arguably the most powerful feature of MicroStrategy is that it is Aggregate Aware.  Since it writes ROLAP SQL, you as the Architect have the ability to simply drop in an Aggregate Table and MicroStrategy will automatically use it when appropriate.  The amount of development time required to increase the performance of your reports across the board is minimal. Today, I’l talk about what Aggregate Tables are and...

dropbox1 0

Developing With Version Control Using Dropbox

Anyone who has done any kind of programming will attest to the value of version control (a feature that is sorely missing from MicroStrategy, but that’s a discussion for another day).  For me, when developing in Flex or Java, using some level of version control has saved me on many occasions.  To be specific, version control is the ability to view different versions of source code...

17

Deploying MicroStrategy Widgets as Plugins

There are a few different ways to deploy your widget from Flex to MicroStrategy.  The easiest, in my opinion, is to simply use the Deploy menu directly from Flex Builder.  This will handle all of the configurations you need on web, and even place the SWF in the proper locations if you can directly map to them (if not, it’s a simple copy/paste).  Another option...

6

Tagging User Email Addresses

In MicroStrategy 9.0, Web Subscriptions were moved from Narrowcast into the Intelligence Server in a new function called Distribution Services.  In the Narrowcast days, you had to maintain a separate metadata of user accounts and rely on a link between User and Email address.  Today, those are more tightly integrated, and the results is having Email addresses directly tied to User accounts as well as...