Explore topic-wise InterviewSolutions in Current Affairs.

Microstrategy DESKTOP installs in MINUTES and automatically presents a list of AVAILABLE Microstrategy Intelligence Servers. Within an hour, the INSTALLATION and SETUP are completed.

Microstrategy Desktop installs in minutes and automatically presents a list of available Microstrategy Intelligence Servers. Within an hour, the installation and setup are completed.

Further INFORMATION can be found in the release notes, as WELL as in MICROSTRATEGY Object MANAGER's online HELP.

Further information can be found in the release notes, as well as in MicroStrategy Object Manager's online help.

If the owner of the SOURCE OBJECT does not exist in the destination project, the user LOGIN for the destination project TAKES ownership of the object when it is copied or replaced.

If the owner of the source object does not exist in the destination project, the user login for the destination project takes ownership of the object when it is copied or replaced.

If the LOCATION exists in the destination project, the DEPENDENT object is COPIED to that location. If the location does not exist in the destination project, a new FOLDER entitled 'Dependencies' is CREATED and the object is copied to that folder.

If the location exists in the destination project, the dependent object is copied to that location. If the location does not exist in the destination project, a new folder entitled 'Dependencies' is created and the object is copied to that folder.

Tracing is available under the Tools/Diagnostics MENU. These tracing options apply to every MicroStrategy product installed on the machine.

To SEE the SQL that has been executed against the metadata, go to the ADVANCED tab and turn on 'SQL Tracing' under the DSS MDServer key.

Function level tracing can be accomplished by going to the Advanced tab and turning on 'Function Level Tracing' under the DSS ObjectManager key.

Tracing is available under the Tools/Diagnostics menu. These tracing options apply to every MicroStrategy product installed on the machine.

To see the SQL that has been executed against the metadata, go to the Advanced tab and turn on 'SQL Tracing' under the DSS MDServer key.

Function level tracing can be accomplished by going to the Advanced tab and turning on 'Function Level Tracing' under the DSS ObjectManager key.

USING MicroStrategy Object Manager to copy/move objects around is not RECOMMENDED while other USER sessions are making CHANGES using MicroStrategy Agent, as it could lead to metadata INCONSISTENCY. Project and schema locking prevent multiple users sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring.

Using MicroStrategy Object Manager to copy/move objects around is not recommended while other user sessions are making changes using MicroStrategy Agent, as it could lead to metadata inconsistency. Project and schema locking prevent multiple users sessions from manipulating the schema at the same time. This prevents metadata inconsistency from occurring.

Security in MicroStrategy Object Manager is based on the MicroStrategy 7.x PRODUCT Suite security model. All activities that can be performed in MicroStrategy Object Manager are governed by privileges and access control lists. For example, if a user is not ALLOWED to access a certain folder in MicroStrategy AGENT, they will not be able to access the folder in MicroStrategy Object Manager.

Security in MicroStrategy Object Manager is based on the MicroStrategy 7.x Product Suite security model. All activities that can be performed in MicroStrategy Object Manager are governed by privileges and access control lists. For example, if a user is not allowed to access a certain folder in MicroStrategy Agent, they will not be able to access the folder in MicroStrategy Object Manager.

Yes, schema objects can be copied across PROJECTS using MicroStrategy Object Manager. MicroStrategy Object Manager moves objects seamlessly between similar projects such as from a development project version to a production project version where the warehouses are the same in terms of views, prefixes, and warehouse structure. However, subtle changes in the warehouse that relate to prefixes, views, or table structure cannot be tracked by MicroStrategy Object Manager. For situations where the projects' warehouse structures or setups are dissimilar, USERS may be required to make further edits of the objects to ENSURE FULL integration into the destination project. These edits may include hierarchical relationship changes or modifications to the prefixes.

Yes, schema objects can be copied across projects using MicroStrategy Object Manager. MicroStrategy Object Manager moves objects seamlessly between similar projects such as from a development project version to a production project version where the warehouses are the same in terms of views, prefixes, and warehouse structure. However, subtle changes in the warehouse that relate to prefixes, views, or table structure cannot be tracked by MicroStrategy Object Manager. For situations where the projects' warehouse structures or setups are dissimilar, users may be required to make further edits of the objects to ensure full integration into the destination project. These edits may include hierarchical relationship changes or modifications to the prefixes.

MicroStrategy OBJECT Manager makes a list of all object dependencies before COPYING an object to prevent metadata inconsistency. The time required for dependency checking VARIES based on a CUSTOMER's metadata size and SCHEMA complexity. For large metadata and complex schemas, gathering all the dependencies may take a long time.

MicroStrategy Object Manager makes a list of all object dependencies before copying an object to prevent metadata inconsistency. The time required for dependency checking varies based on a customer's metadata size and schema complexity. For large metadata and complex schemas, gathering all the dependencies may take a long time.

To VIEW the OBJECT ID of an object, right-mouse click on the object and SELECT 'Properties.' The Object ID and Version ID are listed on the 'General' tab.

To view the Object ID of an object, right-mouse click on the object and select 'Properties.' The Object ID and Version ID are listed on the 'General' tab.

To determine if two objects are the same, MicroStrategy Object Manager COMPARES their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution GRID LISTS the conflict as 'Exists Identically.' If the Version ID's are DIFFERENT, the Conflict Resolution grid lists the conflict as 'Exists Differently.'

To determine if two objects are the same, MicroStrategy Object Manager compares their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution grid lists the conflict as 'Exists Identically.' If the Version ID's are different, the Conflict Resolution grid lists the conflict as 'Exists Differently.'

The CONFLICT Resolution WINDOW provides the user with a means to decide how to handle object conflicts between the source project and the destination project. In addition, the Conflict Resolution window displays the object name in the original project, the object name in the destination project and the type of conflict. Users may also specify a NEW name for the object DEPENDING on the action CHOOSEN.

The Conflict Resolution window provides the user with a means to decide how to handle object conflicts between the source project and the destination project. In addition, the Conflict Resolution window displays the object name in the original project, the object name in the destination project and the type of conflict. Users may also specify a new name for the object depending on the action choosen.

If a user tries to perform cross-project operations between TWO unrelated projects, MICROSTRATEGY Object Manager will not permit the operation and will display the following error:

Objects cannot be COPIED across the projects because these two projects, "Project name of the source" and "Project name of the destination", have not been CREATED from the same source.

If a user tries to perform cross-project operations between two unrelated projects, MicroStrategy Object Manager will not permit the operation and will display the following error:

Objects cannot be copied across the projects because these two projects, "Project name of the source" and "Project name of the destination", have not been created from the same source.

MicroStrategy OBJECT MANAGER COMPARES the Schema ID's of the two PROJECTS. Duplicated projects have different Project ID's, but their Schema ID's are the same.

MicroStrategy Object Manager compares the Schema ID's of the two projects. Duplicated projects have different Project ID's, but their Schema ID's are the same.

Yes. In ORDER to perform cross-project OPERATIONS, the projects involved must ORIGINATE from the same source project. In other words, the projects can only be related by the duplication of a single project. This ensures that the projects have a similar set of schema and application objects, and that the object ID's in the two projects are the same. MICROSTRATEGY Object MANAGER uses the object and version ID's across the projects to perform comparisons. MicroStrategy Object Manager prevents the user from attempting operations across unrelated projects.

Yes. In order to perform cross-project operations, the projects involved must originate from the same source project. In other words, the projects can only be related by the duplication of a single project. This ensures that the projects have a similar set of schema and application objects, and that the object ID's in the two projects are the same. MicroStrategy Object Manager uses the object and version ID's across the projects to perform comparisons. MicroStrategy Object Manager prevents the user from attempting operations across unrelated projects.

MICROSTRATEGY Administrator - Object Manager allows users to perform the following actions:
• Duplicate and upgrade PROJECTS
• Copy objects within and across RELATED projects
• Move objects within a project
• Delete objects within a project
• RENAME objects within a project
• Search for objects within a project
• Find an object's parents or CHILDREN within a project.

MicroStrategy Administrator - Object Manager allows users to perform the following actions:
• Duplicate and upgrade projects
• Copy objects within and across related projects
• Move objects within a project
• Delete objects within a project
• Rename objects within a project
• Search for objects within a project
• Find an object's parents or children within a project.

Security FILTER is used to apply security at the database data level.Whenever a users associated with security filter runs a REPORT, a WHERE clause is always INCLUDED in the report SQL with the condition DEFINED in the Security Filter.

Security filter is used to apply security at the database data level.Whenever a users associated with security filter runs a report, a WHERE clause is always included in the report sql with the condition defined in the Security Filter.

Pass through functions are used to UTILIZE VARIOUS special functions that SPECIFIC to databases.Some of the passthrough functions available are Applysimple and Applycomparision.

Pass through functions are used to utilize various special functions that specific to databases.Some of the passthrough functions available are Applysimple and Applycomparision.

CUSTOM groups are used to create different FILTERS to different rows of a report.For EXAMPLE, a report can created to display top 5 customers as well as bottom 5 customers in the one report USING custom group.

Custom groups are used to create different filters to different rows of a report.For example, a report can created to display top 5 customers as well as bottom 5 customers in the one report using custom group.

Consloidations ENABLE to group together attibute ELEMENTS and create a virtual attribute.They PERFORM ROW level maths.

Consloidations enable to group together attibute elements and create a virtual attribute.They perform Row level maths.

Using VLDB properties we can change the way how the SQL is generated.Some of them are below:
Perform full outer joins
Check for Zeros and NULLS in the denominator while performing divisions in METRICS.
Creating SUB queries
Creating temperory tables.

Using VLDB properties we can change the way how the SQL is generated.Some of them are below:
Perform full outer joins
Check for Zeros and Nulls in the denominator while performing divisions in Metrics.
Creating Sub queries
Creating temperory tables.

Adhoc reports run in REAL time based on the input parameters PROVIDED by the USER at the run time.In Microstrategy, adhoc reports are created using Prompts.

In static reports, users won't be PROVIDE any input parameters.These reports are usaully schedule to run overnight and ready to VIEW immediatley in the mornings using cache.

Adhoc reports run in real time based on the input parameters provided by the user at the run time.In Microstrategy, adhoc reports are created using Prompts.

In static reports, users won't be provide any input parameters.These reports are usaully schedule to run overnight and ready to view immediatley in the mornings using cache.

In 2 TIER ARCHITECTURE, the MicroStrategy Desktop itself queries aganist the Data warehoue and the Metadata with out the INTERMEDIATE tier of the Intelligence server.

The 3 Tier architecture comprises a Intelligence server between MicroStrategy Desktop and the data Warehouse and the Metadata.

The 4 tier architecture is same as 3 tier except it has a additional COMPONENT of MicroStratey Web.

In 2 tier architecture, the MicroStrategy Desktop itself queries aganist the Data warehoue and the Metadata with out the Intermediate tier of the Intelligence server.

The 3 Tier architecture comprises a Intelligence server between MicroStrategy Desktop and the data Warehouse and the Metadata.

The 4 tier architecture is same as 3 tier except it has a additional component of MicroStratey Web.

Star Schema Advantages: Reduces the number of JOINS between the tables and HENCE faster performance.

Star Schema Disadvantages:Requires Most amount of storage SPACE.

SNOWFLAKE Schema Advantages: Minimum storage space and minimum data redundancy.

Snowflake Schema Disadvantages:Requires more joins to get information from LOOK up tables hence slow performance.

Star Schema Advantages: Reduces the number of joins between the tables and hence faster performance.

Star Schema Disadvantages:Requires Most amount of storage space.

Snowflake Schema Advantages: Minimum storage space and minimum data redundancy.

Snowflake Schema Disadvantages:Requires more joins to get information from look up tables hence slow performance.

Star SCHEMA is a HIGHLY denormalized schema whereas SNOWFLAKE schema is hight NORMALIZED schema.Star schema is CHARACTERIZED by large number of rows in a table and less number of joins between tables.Snowflake schema is characterized by less number of rows in a table while more number of joins between tables.

Star Schema is a highly denormalized schema whereas snowflake schema is hight normalized schema.Star schema is characterized by large number of rows in a table and less number of joins between tables.Snowflake schema is characterized by less number of rows in a table while more number of joins between tables.

ROLAP (Relational online Analytical Processing) tools do not use pre-calculated DATA cubes. Instead, they intercept the query and pose the question to the standard relational database and its tables in order to bring back the data required to answer the question.

MOLAP (Multidimensional online Analytical Processing) tools utilize a pre-calculated data SET, COMMONLY referred to as a data cube, that contains all the possible answers to a given range of QUESTIONS.

MicroStartegy is ROLAP tool.

ROLAP (Relational online Analytical Processing) tools do not use pre-calculated data cubes. Instead, they intercept the query and pose the question to the standard relational database and its tables in order to bring back the data required to answer the question.

MOLAP (Multidimensional online Analytical Processing) tools utilize a pre-calculated data set, commonly referred to as a data cube, that contains all the possible answers to a given range of questions.

MicroStartegy is ROLAP tool.

'Pick FIRST GROUP'.

'Pick First Group'.

• Sending HTTP response, confirming an email/jms MESSAGE ETC. This is because the CONFIRMATION or sending HTTP response has to done in the same session. When engine crashes these sessions are CLOSED at their socket level. In such CASES send response/confirm before checkpoint.

• Sending HTTP response, confirming an email/jms message etc. This is because the confirmation or sending HTTP response has to done in the same session. When engine crashes these sessions are closed at their socket level. In such cases send response/confirm before checkpoint.

$_error variable is AVAILABLE in the node following the error TRANSITION. It captures the error message, error code ETC.

$_error variable is available in the node following the error transition. It captures the error message, error code etc.

• XML
• HTML
• TEXT

• XML
• HTML
• Text

Child AXIS- What this MEANS is that when you SELECT "BOOK" from the CURRENT context, it selects a child node with that NAME, not a sibling with that name. Other axes are parent , self , sibling etc.

Child axis- What this means is that when you select "BOOK" from the current context, it selects a child node with that name, not a sibling with that name. Other axes are parent , self , sibling etc.

Basically wait and notify should SHARE a common notification configuration which is just a schema definition for data that will be passed from NOTIFIER to waiter. SPECIFIC instances of waiter & notifier are corrrelated via a KEY.
For example: when one process is in wait state for key 'Order-1', it waits till another process issues a notification with the same key value.

Basically wait and notify should share a common notification configuration which is just a schema definition for data that will be passed from notifier to waiter. Specific instances of waiter & notifier are corrrelated via a key.
For example: when one process is in wait state for key 'Order-1', it waits till another process issues a notification with the same key value.

• Both of them can be manipulated via the palette resources 'Get shared variable' and 'Set shared variable'.
• A job shared variable is private to one INSTANCE of job or in other words each job has a fresh COPY. In the case of shared variable the same copy is shared across all job instances. It can even be persisted and can survive BW ENGINE restarts and even shared across multiple BW engines(when deployed using DB persistence).

• Both of them can be manipulated via the palette resources 'Get shared variable' and 'Set shared variable'.
• A job shared variable is private to one instance of job or in other words each job has a fresh copy. In the case of shared variable the same copy is shared across all job instances. It can even be persisted and can survive BW engine restarts and even shared across multiple BW engines(when deployed using DB persistence).

The SCOPE of USER defined PROCESS variables is only the process in which it is defined.(Not EVEN INSIDE a sub process that is invoked from this process)

The scope of user defined process variables is only the process in which it is defined.(Not even inside a sub process that is invoked from this process)

SOAP REQUEST reply activity. If the business process needs to be exposed as SOAP SERVICE use SOAP Event SOURCE in CONJUNCTION with SOAP Send Reply or SOAP Send Fault.

SOAP request reply activity. If the business process needs to be exposed as SOAP service use SOAP Event Source in conjunction with SOAP Send Reply or SOAP Send Fault.

TYPES of ADAPTER services are :
• Subscriber SERVICE
• PUBLISHER Service
• Request-Response Service
• Request-Response Invocation Service .

Types of adapter services are :
• Subscriber Service
• Publisher Service
• Request-Response Service
• Request-Response Invocation Service .

HTTP Receiver. In this case the receiver on new machine starts LISTENING on the same port, but you NEED to REDIRECT REQUESTS from the old machine to the new one.

HTTP Receiver. In this case the receiver on new machine starts listening on the same port, but you need to redirect requests from the old machine to the new one.

CheckPoint activity - Specify the uniqueID for the duplicate key field and ENGINE maintains list of these key fields. When a process come to checkpoint activity with the same VALUE for duplicate key which already exists, it THROWS a DuplicateException. An error transition can then HANDLE this case.

CheckPoint activity - Specify the uniqueID for the duplicate key field and engine maintains list of these key fields. When a process come to checkpoint activity with the same value for duplicate key which already exists, it throws a DuplicateException. An error transition can then handle this case.

When you HANDLE an error inside a called SUBPROCESS or group and WANT to rethrow the error to the caller (happens by default if you dont handle the error in the called process)

When you handle an error inside a called subprocess or group and want to rethrow the error to the caller (happens by default if you dont handle the error in the called process)

We can USE REPEAT on ERROR until TRUE.

We can use Repeat on Error until true.

The three scenarios are:
• SHARED Variables across BW ENGINES.
• Locking across groups in MULTIPLE BW engines.
• Wait Notify across BW engines.

The three scenarios are:
• Shared Variables across BW engines.
• Locking across groups in multiple BW engines.
• Wait Notify across BW engines.

This can be accomplished USING job shared variables, UNLESS in the call process activity the 'Spawn' FLAG is enabled in which case the called sub process is a new job and hence gets a fresh copy of the job shared variable initialized as per its configuration. A shared variable can overcome this limitation as it's scope is not limited to ONE job.

This can be accomplished using job shared variables, unless in the call process activity the 'Spawn' flag is enabled in which case the called sub process is a new job and hence gets a fresh copy of the job shared variable initialized as per its configuration. A shared variable can overcome this limitation as it's scope is not limited to one job.

• $_globalVariables
• $_processContext

• $_globalVariables
• $_processContext

The 'Assign' activity can be used to set the VALUE of a 'User DEFINED process VARIABLE'.

The 'Assign' activity can be used to set the value of a 'User defined process variable'.

'No ACTION' GROUP used to have a SET of activities having a COMMON ERROR transition

'No Action' group used to have a set of activities having a common error transition

No. There can be only one Error and one SUCCESS if no MATCHING CONDITION transition out of each ACTIVITY.

No. There can be only one Error and one Success if no matching condition transition out of each activity.

Use the SEQUENCING key FIELD in the MISC tab of any process starter. Process INSTANCES with the same value for this field are executed in the sequence in which they are started.

Use the sequencing key field in the Misc tab of any process starter. Process instances with the same value for this field are executed in the sequence in which they are started.

A Lock is specified for a 'Critical Section' group when the scope is 'Multiple'. It can be used to ensure SYNCHRONIZATION across PROCESS instances belonging to multiple processs definitions or for process instances across engines(CHECK multi ENGINE flag for lock in this CASE and the BW engine needs to be configured with database persistence while deployment). If synchronization is for process instances belonging to the same processs definition inside one engine, just specify the scope as 'Single'.

A Lock is specified for a 'Critical Section' group when the scope is 'Multiple'. It can be used to ensure synchronization across process instances belonging to multiple processs definitions or for process instances across engines(Check multi engine flag for lock in this case and the BW engine needs to be configured with database persistence while deployment). If synchronization is for process instances belonging to the same processs definition inside one engine, just specify the scope as 'Single'.

Uses of GROUPING activities are:
• Create a set of activities having a common error transition.
• Repeat group of activities based on a condition.
1. Iterate over a list.
2. Repeat until condition TRUE.
3. Repeat on Error until condition true.
• Group activities into a transaction.
• To create a critical SECTION area that SYNCHRONIZES process instances.
• A 'Pick First Group' allows you to wait for the occurence of multiple events and proceed along a PATH following the first event to occur.

Uses of grouping activities are:
• Create a set of activities having a common error transition.
• Repeat group of activities based on a condition.
1. Iterate over a list.
2. Repeat until condition true.
3. Repeat on Error until condition true.
• Group activities into a transaction.
• To create a critical section area that synchronizes process instances.
• A 'Pick First Group' allows you to wait for the occurence of multiple events and proceed along a path following the first event to occur.

The options for CONFIGURING STORAGE for process engine's CHECKPOINT repository are:
• Peer means all of them have the same weight. In this CASE when one engine fails another one takes over and continues processing till it fails.
• In master secondary CONFIGURATION weights are unequal, the secondary starts processing when master fails. But when master recovers, secondary stops and master continues processing.

The options for configuring storage for process engine's checkpoint repository are:
• Peer means all of them have the same weight. In this case when one engine fails another one takes over and continues processing till it fails.
• In master secondary configuration weights are unequal, the secondary starts processing when master fails. But when master recovers, secondary stops and master continues processing.