Re: Some body know the impact in performance of unused database options installed
- From: Hans Forbrich <fuzzy.graybeard@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Mon, 20 Oct 2014 15:55:32 -0600
Depends on what you define as overhead.
If I understand your suggestion, it's basically a DI Y project Which
means the overhead is in starting, implementing, and maintaining the
'kernel' and any features/capabilities.
Which puts it somewhere around the Berkeley or MySQL arena, right?
And when 'you' implement the PL/SQL capabilities, you can then start
down the "what are the attack vectors inadvertently created" road ...
Personally, I think Oracle server is far less expensive. ;-)
/Hans
On 20/10/2014 1:40 PM, Iggy Fernandez wrote:
At the risk of being booed, I cannot help thinking that the database
with the least overhead as well as the most secure is one that has no
data dictionary or options whatsoever; that is, one created with
CREATE DATABASE and nothing else. Yes, you will be able to create
users, tables, indexes, etc but you will have no data dictionary
whatsoever. No DBA_TABLES. No overhead and no "attack vectors" either.
Am I completely crazy? Stark raving mad?
Iggy
P.S. With just a little extra, you will be able to create PL/SQL
functions, procedures, and triggers.
Other related posts:
