A friend of mine caught this link on LifeHack…Free Tableau Public…Interesting enough to play around with as long as you’re not playing with private data.
Been gearing up for finals oh loyal reader base of 3 people. I’ll get to development…during spring break (this is how I party).
Another in the “Basic” series (because that’s about my knowledge level) .
One of the things that you might come across as an Administrator or a Project Manager is a “Time Out Error”. Now most Architects or Project management people will set this in such a way that it allows for your reports to develop, but also times out if your users somehow manage to work themselves into some sort of weird outer cross join magic.
So, say the standard 10 minutes on install isn’t enough because you’re dealing with a million rows joined to 13 tables. (It happens. Trust Me.)
Right click on your project name and select Project Configuration. Or, highlight the project you want to adjust and under the Administration Menu, select Project Configuration.
You can click through to the image below for a larger view.
On the left hand side the third option down is called Governing. This is in MicroStrategy 9 by the way, so it might be slightly different order in 8. The first option is called Results Set. As you can see in the highlighted section, this is where your interactive and scheduled reports timing is governed. Adjust them based on seconds. Keep in mind, if you make it too high, you’re going to have a cranky analyst calling and asking why his report won’t stop running, as opposed to why his report just timed out. Either way, remember it’s his fault.
I have recently gained the Permanent Resident status for Canada and I will be moving in Toronto next month. Hurray!!! 
So if you are one of our frequent readers from GTA and you just happen to know a place well suited for an experienced and innovative MicroStrategy developer, please contact me at ssorin@gmail.com or check out my full profile at http://www.linkedin.com/in/sorinsuciu.
While the merge with Object Tracking Tool is still in development, I am proud to introduce the new and improved version of Metadata Browser, which you can download here: MBsetupV2.0.exe
Improved Documentation Tool
New properties are now retrieved for common object types:
Change Journal Tools
This new function only works with MicroStrategy version 9.0 or higher and it either shows the Change Journal entries for a single object or for all the objects in a particular folder.
God Mode
If you have admin rights you can connect using “God Mode” and thus gain access to hidden system files. An interesting use (found during the test phase) is to navigate to System Objects\Columns and make dependency searches directly on Columns.
This is a read only application. Using it won’t cause any changes to your Metadata.
I remember it well. Long night spent trying to figure out how best to line metrics up next to each other. Hours spend trying to figure out if it’s more work just creating you’re own logical table to solve that stupid cross join problem that won’t go away. I’m reticent to consult the MicroStrategy web site because it really does just feel like I’m copping out…
If you have a static warehouse that the designers are committed to, what else is your option?
Late night..
Addendum: You know sometimes I forget that SQL optimization is just that…optimization. I can some time putting together a quality query that’s going to return data on a specific products ships and returns. Let’s assume that each of these products have a distinct way of being tracked. I might throw together a hand done query that populates the list of these specific reference numbers from the ship table so that I can do a left join against the shipping data so I can see specific returns against the specific ships, and then aggregate those solutions, but did you see what I just did? I went through the trouble of matching thousands of records against each other…and for what? So that I can later aggregate the data with some sort of group by.
Enter SQL optimization. Solves the problem in a quicker way that I probably wouldn’t have crossed my mind since it works in a linear fashion.
But…why is the detail necessary?
MicroStrategy fixes.
(
select a12.date,
count(a11.sales_number) SALES_COUNT
from sales a11
where (a11.item_desc = ‘widget’)
group by
a11.date
) pa11
full outer join
(
select a11.date,
count(a11.rma_number) RMA_COUNT
from rma a11)
where (a11.item_desc = ‘widget’)
group by
a11.date
) pa12
on
(pa11.date = pa12.date)
Makes much more sense. Why join early when all you care about is the aggregate…join on the aggregate!
Duh.
Recent Comments