• All
  • Advanced Analytics
  • AI & LLM
  • Amazon
  • Big Data & Cloud
  • ClearPeaks
  • Cloudera
  • CoolThoughts
  • Data Governance
  • Enterprise BI
  • ETL
  • Executive Analytics
  • Google
  • Informatica
  • KNIME
  • Microsoft
  • Observation Deck
  • Oracle
  • Qlik
  • Snowflake
  • Tableau
  • Visualizations
  • Web & Mobile BI Development

I’ve recently been assigned to a customer project where I was in charge of the BI System Administration. The project was in the user acceptance stage and changes to reports & dashboards happened very frequently.

 

One of my daily tasks involved moving the latest web catalog changes from a development instance (where the latest user requirements were covered) to the user testing environment.

To mention that security played a very important role during these migrations since the web catalog privileges had to remain untouched within the target environment.

 

Most of the companies that use BI as the enterprise reporting tool require a row level security mechanism. At this stage, it is important to bear in mind that the row level security has nothing to do with the user authorization to see the different reports or dashboards but its main target is to limit the data that the users can see. It is essential that the process of granting the right access to users runs seamlessly in the background. This can be implemented in OBIEE 11g and this article explains how this can be achieved.
Loading new posts...
No more posts