Submitted by John Watson on Sat, 2015-10-10 06:01
Proxy authentication has been around since release 9i, but it isn't widely used. It can be a very useful facility for giving certain users access to high privileges without having to give them any direct grants or roles, and avoids many of the problems of using shared accounts. It is of course fully audited.
Submitted by John Watson on Mon, 2015-09-07 10:46
Standard Edition release 22.214.171.124 is now available. Download it from the usual locations. But along with the great news, comes some news that is not so great: the licensing model has changed.
Submitted by John Watson on Sat, 2015-07-25 10:00
Following previous blog re BASIC compression, here are a couple of simple tests with Advanced Compression - which is supposed to survive conventional DML.
Submitted by John Watson on Thu, 2015-07-09 11:59
BASIC table compression is included with Enterprise edition, and can achieve respectable compression ratios. But beware! Subsequent DML may be disastrous.
Submitted by sramawat on Thu, 2015-06-18 02:12
This paper provides best practices for rapid deployment of Oracle Database Vault protections to
secure sensitive application data inside the database. Oracle Database Vault enables you to restrict administrative access to an Oracle
database. This helps you address the most difficult security problems remaining
today: protecting against insider threats, meeting regulatory compliance
requirements, and enforcing separation of duty. It covers the following main topics:
Submitted by John Watson on Sat, 2015-04-25 13:56
The ability to quiesce the database was introduced in release 9, but to this day I find that many people are not aware of it. It can be really useful - so let's describe it. I'll begin by positioning the quiesce capability: when is it useful. Then detail how to do it, then reverse engineer the mechanism.
Submitted by John Watson on Wed, 2015-04-08 11:50
Excellent book - I've just posted this review on Amazon:
Submitted by MarcMartens on Tue, 2015-02-24 06:41
Why publishing this under SQL instead of RDBMS Server?
The necessaty to create supporting indexes for foreign keys has been explained in other articles.
However writing a foolproof query to identify missing FK indexes is not so straightforward as it might look. I used to do it PLSQL, but this has proven not to scale very well and taking quite some elapsed time and system resources in databases with many thousands of tables. The blog entry is about the challenge to get the job done with a well performing SQL statement.
Submitted by John Watson on Sat, 2015-02-21 08:12
Another example of what I think of as "the self-tuning database". Setting optimizer_dynamic_sampling=11 can fix many performance problems, without the DBA needing to use his brain at all.
Submitted by John Watson on Sun, 2015-02-08 07:48
Excellent exposition of a very effective SQL tuning metodology