This is simply amazing.I am new in the Microstrategy world and was stuck how to map Attribute with fact table but this video really solved the problem.Thank you for the help.
@JamesOliver5 жыл бұрын
Glad I was able to help and I appreciate the kind words very much! :)
@SaadQureshiOfficial5 жыл бұрын
@@JamesOliver One thing I have noticed,If we haven't mapped attribute and facts and try to present the information in the report,it will do a cross join.
@JamesOliver5 жыл бұрын
@@SaadQureshiOfficial Yea cross join can be an indication of an issue with relationships.
@venkatm1402 жыл бұрын
Kudos and best videos for Microstrategy for everybody. Time and again thanks for your help and great content....Much respect....
@nitintomer59236 жыл бұрын
Great video focusing on almost all part of architect.
@JamesOliver6 жыл бұрын
Thank you! And thanks for subscribing!
@sauravchaudhury8026 жыл бұрын
This is gr8 James.. just 1 request , can you please make a video on a) Architecting Many to Many relationship b) setting up the metadata for microstrategy
@mendemende85394 жыл бұрын
good job! I like to watch your videos and please keep doing it!
@JamesOliver4 жыл бұрын
I appreciate the kind words :)
@obaidsatti60014 жыл бұрын
This video is very informative, I nave a question. How I can add a secondary DB Instance?
@NR-el6ht6 жыл бұрын
Nice good job ... hope you will do more admin and architect related work as well...and will expect more deep way of architect work... thanks
@JamesOliver6 жыл бұрын
Thanks! Yes I will definitely be doing more architect videos. Make sure to subscribe!
@NR-el6ht6 жыл бұрын
@@JamesOliver ..subscribed..
@yaseersayeed12152 жыл бұрын
how the passes is increase to 5 for single attribulte and metric plz expain on it how to find that so
@ismailacisse93086 жыл бұрын
Million Euro Video !! Thanks !
@JamesOliver6 жыл бұрын
Thank you! Please subscribe if you haven't already.
@vikramavirneni45616 жыл бұрын
Excellent expecting more videos on MicroStrategy developer roles from you please be active .
@JamesOliver6 жыл бұрын
Thank you! I'm really trying to grow this channel and I do enjoy making these videos. I plan to make many more videos. My next video coming out soon will be about dashboards. It will also incorporate aspects of some of my other videos.
@sreism6 жыл бұрын
How do we know which table to use as set as lookup table and how the set us lookup table will reflect in the join condition ,thanks
@JamesOliver6 жыл бұрын
The lookup table should be the table where each record represents an attribute element or value. For example, if you are a retailer with stores, then your store attributes lookup table would be your store master table. In this table there should be 1 record for each store. This table would also contain the store #, store description, etc. Now, when whenever the report needs to pull in values pertaining to a store, like for example Store Name/Description, it will join to this table by default. Even if store name is on some other table, it will always use the lookup table.
@sreism6 жыл бұрын
Nice
@aeronridgeway68024 жыл бұрын
how about starting with what it is?
@JamesOliver4 жыл бұрын
hmm.. guess I assumed anyone interested in watching this video would already know.. lol.