Thanks Mark.
On Friday, June 25, 2021, 02:34:42 PM EDT, Powell, Mark
<mark.powell2@xxxxxxx> wrote:
#yiv1008427804 P {margin-top:0;margin-bottom:0;}Sanjay, it seems to me that
both options are available to you. I think how the users are going to access
the data will determine which option you choose. If all access is via an ad
hoc reporting tool then the view approach works well, but if the access is to
be from one application screen for all users, then you probably want to use VPD.
Mark PowellDatabase Administration(313) 592-5148
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx>
Sent: Thursday, June 24, 2021 1:26 PM
To: Oracle List <oracle-l@xxxxxxxxxxxxx>
Subject: Oracle VPD Hi Everyone
I am working on masking/restricting data access to certain users on multiple
tables based on some column data filtering. Schema1.Table1 has column mfg_data
where I need to block access based on values to certain reporting users.
Question is that there are multiple tables and filtering is based on same
column in all tables and so I need to explore if 1. I can use view on all of
these table with filtering the required data and assign only access to these
views to Reporting users 2. Or do the VPD setup to control it.
Need to get Pros and cons of both option based on Performance as it will be on
multiple tables. Also any reported bug or issue with the usage like performance
or using VPD and DBMS_redef or MV refresh or so
Please share your experience
TxSanjay
