New answers tagged


SQL Server stores Active Directory users using their GUID which won't change when you alter the name in AD, so no worries.


You cannot filter on the AD group. This previous question explains how the access management works with AD groups: How to tell which windows group login I used when logging in via windows authentication


I would use regex_like: select column_value , case when regexp_like(' '||column_value||' ','\s(drop|execute|truncate|create|insert|update|delete|merge)\s', 'i') then 'Yes' end as illegal from table(ora_mining_varchar2_nt ('drop table customers', 'just dropping by', 'undroppable')); COLUMN_VALUE ...


I'm not sure there is a good answer. In general, string concatenation to build your SQL is always a bad idea and should be avoided whenever possible. That said, it would be difficult to avoid in your case except for replacing user_id references with bind variables. Other than that, you will have to come up with some custom logic to validate the content of ...


Using LD_PRELOAD to implement a hidden trojan in an oracle database You can also follow the links there. Like this one:

Top 50 recent answers are included