What Are The Various Ways Of Incorporating Security In Microstrategy?

1.	What Are The Various Ways Of Incorporating Security In Microstrategy?
Answer» In Microstrategy security can be incorporated using a mix of any of the following WAYS: 1. Putting USER specific restrictions at the database end and using user specific connection mapping. This is for column level security. 2. Applying folder and object level security to restrict ACCESS to CERTAIN set of reports/objects 3. Applying Security filters to the user. This provides row level security. In Microstrategy security can be incorporated using a mix of any of the following ways: 1. Putting user specific restrictions at the database end and using user specific connection mapping. This is for column level security. 2. Applying folder and object level security to restrict access to certain set of reports/objects 3. Applying Security filters to the user. This provides row level security.

Answer»

In Microstrategy security can be incorporated using a mix of any of the following WAYS:
1. Putting USER specific restrictions at the database end and using user specific connection mapping. This is for column level security.
2. Applying folder and object level security to restrict ACCESS to CERTAIN set of reports/objects
3. Applying Security filters to the user. This provides row level security.

In Microstrategy security can be incorporated using a mix of any of the following ways:
1. Putting user specific restrictions at the database end and using user specific connection mapping. This is for column level security.
2. Applying folder and object level security to restrict access to certain set of reports/objects
3. Applying Security filters to the user. This provides row level security.

Discussion

No Comment Found

Related InterviewSolutions

What Is A Materialized View?
How To Reduce Multiple Passes To One In A Report?
I Have A Fact Table At All Time Levels(date, Week...year). I Have The Similar Fact Table At Year Level. If I Create A Report With A Fact Attribute And A Metric Based On That Fact........ How Do We Force The Mstr To Use Year Level Fact Table Instead Of Using The All-levels Fact Table?
If We Need To Restrict Certain Columns From Appearing To A User/user-group How Can We Do It?
If We Need To Restrict Certain Rows From Appearing To A User/user-group How Can We Do It?
How Do We Prevent A Cross-join?
What Leads To A Cross-join Or How Does A Cross-join Occur?
When Do We Need To Create A View Or A Materialized View In A Database?
What Kind Of Optimizations You Did?
How Can Users Design Dashboards Quickly And Without Programming Experience Or Training?