[Previous entry: "alpha copies of two chapters of Tom's new book are available"] [Next entry: "Tug has an interesting post on software terrorists"]
Follow up on direct appplication repository access
May 5th, 2005 by Pete
Post to del.icio.us
Post to Furl
I posted about a week ago about direct dictionary access in a post titled "Tom talks about direct dictionary editing" and then again in a post titled "Direct dictionary access again". A few days ago Paul Drake sent me some good advice on the latter post. I wanted to repeat this here for others to benefit. Here it is:
"Pete,
One method of handling application metadata is to segregate it to its
own tablespaces, which are altered to read only except during
application maintenance. If an event trigger is configured to send an
alert when such tablespaces are altered to read write, I think that
most any auditor would be satisfied.
A lot of my employer's lookup data is in small tables anyways, so I had
moved such tables into a 2 KB block size tablespace and set it to read
only. Many of these tables were marked as candidates for single table
hash clusters - so we accomplished several objectives in the move.
Paul"
Thanks Paul for some good advice on managing application repositories.
