|
September , 2004
In
This Issue
|
|
All articles have been reprinted with the written consent of their respective authors.
| ||||||||||||||||
|
||||||||||||||||
|
Data Dictionary for Oracle v2.0 Quest Software presents Data Dictionary for Oracle v2.0, a freeware tool for viewing DBA_View and V$ View information. Use this application to reference Oracle 9.i2 documentation or connect to your own Oracle instance to obtain descriptions and column data from a live system. Click here
for more information. |
||||||||||||||||
|
||||||||||||||||
|
Resolving Oracle Latch Contention
This white paper presents an overview of how the Oracle RDBMS uses latches to protect shared memory, the typical causes of and solutions to latch contention, and summarizes some research conducted at Quest Software that suggests that manipulating the (now) undocumented parameter “_spin_count” can be effective in relieving otherwise intractable latch contention problems.
Click here
for the article. | ||||||||||||||||
|
||||||||||||||||
|
A Practical Implementation of a Real-time Intrusion Prevention System for Commercial Enterprise Databases
Security is becoming one of the most urgent challenges in database research and industry, and there has also been increasing interest in the problem of building accurate data mining models over aggregate data, while protecting privacy at the level of individual records. Instead of building walls around servers or hard drives, a protective layer of encryption is provided around specific sensitive data-items or objects. This prevents outside attacks as well as infiltration from within the server itself. This also allows the security administrator to define which data stored in databases are sensitive and thereby focusing the protection only on the sensitive data, which in turn minimizes the delays or burdens on the system that may occur from other bulk encryption methods. Encryption can provide strong security for data at rest, but developing a database encryption strategy must take many factors into consideration. This paper presents a practical implementation of field level encryption in enterprise database systems, based on research and practical experience from many years of commercial use of cryptography in database security. We present how this column-level database encryption is the only solution that is capable of protecting against external and internal threats, and at the same time meeting all regulatory requirements. We use the key concepts of security dictionary, type transparent cryptography and propose solutions on how to transparently store and search encrypted database fields. In this paper we will outline the different strategies for encrypting stored data so you can make the decision that is best to use in each different situation, for each individual field in your database to be able to practically handle different security and operating requirements. Application code and database schemas are sensitive to changes in the data type and data length. The paper presents a policy driven solution that allows transparent data level encryption that does not change the data field type or length. We focus on how to integrate modern cryptography technology into a relational database management system to solve some major security problems. Click here
for the article. |
||||||||||||||||
|
||||||||||||||||
|
What's My Line? Tracking Exceptions in Oracle10g
It has always been possible in PL/SQL to identify the source of an exception in a block of code; i.e. to know the precise point at which a block of code failed. However, until Oracle 10g, it has not been possible for developers to intervene in the exception in any way whilst retaining this information ( for example to record the exception and its source in application logs ). This has been the cause of many a frustration for developers.
Finally, with the release of 10g, Oracle has added provision for PL/SQL developers to trap AND log exceptions accurately for the first time. The DBMS_UTILITY.FORMAT_ERROR_BACKTRACE function gives us the flexibility we have been demanding for years and the information that the DBMS_UTILITY.FORMAT_ERROR_STACK function simply didn't provide.
Click
here
for the article. |
||||||||||||||||
|
||||||||||||||||
Critical path refers to the sequence of activities that must be completed on schedule for the entire project to be completed on schedule. If the end date for the project has slipped, it is because at least one activity on the critical path did not complete on time. It is important to understand the critical path sequence to know where you have flexibility and where you do not. For instance, you may have a whole series of activities that end up running late, yet the overall project will still complete on time. On the other hand, if your project is falling behind, placing additional resources on non-critical activities will not result in the overall project completing earlier.
Click here
for more information on | ||||||||||||||||
|
||||||||||||||||
|
Free Webcasts |
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
Interactive Crossword
Puzzle: "Greek Mythology"
|
||||||||||||||||
|
||||||||||||||||
|
We love getting white papers, tips, articles, and code examples/archives from our readers around the world. Send your submission to newsletter@quest-pipelines.com. If your article is published, it will be mailed to over 28,000 subscribers. Our mission at Quest Software - RevealNet Labs is to anticipate the daily responsibilities and challenges faced by database professionals. Our products help thousands of people solve problems and implement solutions every day. This newsletter is designed to help facilitate the sharing of information among database professionals. About the Newsletter This newsletter is distributed to Quest Software - RevealNet Labs customers, prospects and friends who have subscribed to it from our website. If you would like to unsubscribe, please visit http://qlist01.quest.com/UnsubMailingList/ Subscribe a Friend! Do you know someone who would like to receive the Pipeline Newsletter? If so, please enter their email address in the box below and click SUBMIT.
Past Issues of the Pipeline Newsletter |
||||||||||||||||
