Warehouse Partition Mapping Table in MicroStrategy

To add and set up a Partition Mapping Table in MicroStrategy:

Step 1: Create the Partition Mapping Table (PMT). Views are not recommended since they defeat the purpose of partitioning and the performance will be hampered instead of improved. Usually the PBTs hold the same structure as the original base fact table.

This table must be created with the following structure:

The ATTRIBUTE_ID column name must match the column name on the partitioned base tables. This column contains the values of the attributes at which the tables are partitioned. Attribute ID(s) used to define the partitioning (partition keys). In addition, the PMT must contain a column named 'PBTNAME' containing the names of each of the partitioned base tables.

For Example, if the partition level is at Year, this column will be named 'Year_id' and contain values such as: 1998, 1999 and 2000.

The PBTNAME column name cannot be changed. This column contains the names of the partitioned base tables. PBTNAME = Partitioned Base Table Name.

Step 2: Add this table to MicroStrategy using Warehouse Catalog. It will be added as a partition mapping table, the icon will change and the number of partitions will be shown in parenthesis. Also, all the corresponding partitions are removed from the list of available tables. The partitions function as a unit; they cannot be deselected individually. Update Schema.

Note: If a prefix is needed to access the PMTs, it has to be included into the mapping table when populating it in WH Catalog.

Step 3: Go to the Partition Mappings folder under Schema Objects. The PMT appears in the right window. Right-click on the table and select edit. Click on the 'Add' button and select the attribute that marks the level of partitioning. Update Schema.

NOTE: (1) The PBTNAME in the Partition Mapping Table (PMT) should be unique. Otherwise, double counting may occur.(2) A PMT is needed for each fact table to be partitioned. (3) A normalized partition base table (PBT) saves database space but it is not recommended if performance is a key issue. The MicroStrategy Engine always applies filters on the partitioned base table queries even if it the filter is a partitioning key.

Clustering in MicroStrategy

Clustering is a popular strategy in which two or more servers/machines are configured to provide common services in a unified manner such that they behave like a single server. Each machine in the cluster is called a node. Even though it may sound very hi-fi, Clustering is one of the simplest thing in MicroStrategy. It aims for Load balancing as well as fail-over. One can cluster Intelligence server running on differ OS. eg, AIX, UX, Solaris, RH Ent Linux provided following condition are met.

1. All MicroStrategy Intelligence Servers MUST point to the same metadata
2. All MicroStrategy Intelligence Servers MUST have the projects in the same state. (i.e., if Node A has Project A in a 'Loaded' state, then Node B must also have Project A in a 'Loaded' state).
3. From each machine where I-server is installed, one should be able to browse the folders for Cache and History List. (This is aachieved by Samba on Unix Environment)
   

You can post here too

To all blog reader,

If you want to be a contributor of this blog or have some interesting article or wihs to share something about MicroStrategy, please ping me and I'll do the needful.

Thanks,
Ashish

Only the dead have seen

Only the dead have seen end of war - Plato

What should you ask your future employer

1. Work days in week? 4 days 5 days or 6 days?
2. How many hours a day?
3. How is salary credited and what day of month?
4. Position/Designation offered?
5. Do they provide free food? Do they have in-house kitchen?
6. Do you give Meal vouchers as part of CTC? How much can I avail? Is there any cap due to position? How and when it is disbursed?
7. Does the job require travel and what if yes what percent?
8. To whom I'll be reporting to and his designation?
9. Relocation reimbursement and the upper limit? T&C.
10. Initial accommodation in a new city? How many days?
11. Dress code? (For me most important question)
12. Number of leaves in a year. Leave policy in detail.
13. How long is probation period?
14. Entitlement of leaves during probation period?
15. Anytime they mentioned year ask about financial or calendar?
16. Joining date?
17. Am I insured by new employer? Are you insured from day 1?
18. Does your parent get Insurance protection (even if it is paid)?
19. Do let them know the time you need to deny/accept the offer.
20. Is LTA an optional component of CTC? If NOT opted, would it be given every month?
21. Do I get an independent extension or shared? If shared among how many people do I need to share?
22. Do I need to work from Home? What’s company policy regarding this? Do you provide laptop/ reimbursement Broadband charges?
23. Do I get unrestricted internet access in office?
24. Can I carry forward my MicroStrategy account?
25. Are you MicroStrategy Inc listed partner?

Migrating a 2 tier project source to a 3 tier source

Technically, you don't really require anything to make a 2 tier, just configure it using configuration manager (your access file). 2 Tier connection is also possible for a Oracle, SQL Server, or any other database.

There are two ways one can migrate a 2 tier (access) based project to Excel.

1. Project duplicate using Project duplication wizard or Object manager.
2. Import the access database into your relational database (Using ETL)

Types of objects in MicroStrategy

There are only and only three types of object in MicroStrategy. they are same follows:

1. Schema
2. Application
3. Configuration

Note: Public objects is just a folder in metadata which "mainly" holds application objects, it is not a type of objects. Security Filter is a configuration object even though it is created the way application objects are created.