|
July, 2003
In
This Issue
|
|
All articles have been reprinted with the written consent of their respective authors. | |||||||||||||
|
|||||||||||||
|
Generic Log Package This script creates a generic procedure that can be used for maintaining a transaction log for audit purposes. Click Here
for the package. |
|||||||||||||
|
|||||||||||||
| More
Examples of Interpreting Wait Events to Boost System Performance Part 3: How Wait Event Information Can be Used to Boost System Performance Roger Schrag & Terry Sutton: Database Specialists, Inc. In early 2002 Roger Schrag published a paper entitled, "Interpreting Wait Events to Boost System Performance." That paper began with a definition of wait events and techniques for collecting wait event information, and then went on to discuss four examples of how wait event data had been used to solve real-life performance problems. The impetus for writing that paper had been that, while many resources were available that listed the wait event v$ views, we were not aware of any publication that actually explained how to use the wait event interface to solve problems or boost system performance. As we write this paper in early 2003, we still are not aware of any such publications. Now Roger Schrag has teamed up with fellow Oracle DBA Terry Sutton to document more examples of how Oracle's wait event interface can be used to solve real-world problems. In essence, this paper is a sequel to last year's paper. If you haven't read the first one, you may view it at http://www.dbspecialists.com/presentations.html. You can read the two papers in either order. In part one of this paper, (found in the May 2003 issue), we defined wait events. In part two of this paper (found in the June 2003 issue), we explained how to collect wait event information. If you have read the previous paper or are already familiar with the wait event interface, we still encourage you to read this section as we've added some enhancements and new details regarding Oracle 9i. In part three of this paper we'll move on to new examples of how wait event information paved the way to solving real-world performance problems. Our feeling is that the more examples of wait event usage you are exposed to, the better position you'll be in to put the wait event interface to work for you when you most need it. Click Here for the article. Encryption
and DBMS_OBFUSCATION_TOOLKIT There are times when data in your system is highly sensitive and it is required that the data is encrypted. Oracle supplies a package called DBMS_OBFUSCATION_TOOLKIT, which allows us to encrypt and decrypt data by applying one of two encryption algorithms and an encryption key. This article should be of interest to both the DBA and developer, especially when designing a new schema where some data is seen to be particularly sensitive. Click Here
for the article. |
|||||||||||||
|
|||||||||||||
|
Creating XML Documents with PL/SQL This article shows some of the possibilities how XML documents can be created with PL/SQL and Oracle 8i or 9i. The discussed topics are:
The examples use the well known tables DEPT (the master table) and EMP (the detail table): Every employee has exactly one department assigned. One department has no, one, or more employees. Click Here for the article.
|
|||||||||||||
|
|||||||||||||
|
SQL Server Upgrade Recommendations and Best Practices The first article of the series, Part 1 – Upgrade Overview and Project Planning, detailed the business justification for upgrades to SQL Server 2000 related to TCO (Total Cost of Ownership), automation capabilities and new features from both the Business and DBA perspectives. The next portion of the article outlined a detailed process to break down the SQL Server 2000 project as well as the applicable Upgrade project phases using high level steps. Both sets of information were in simple terms for DBAs new to the Upgrade process, well experienced DBAs needing a refresher or for technical managers interested in the level of effort and overall planning for a SQL Server 2000 Upgrade. This article, Part 2 – SQL Server 6.5 to 2000 Critical Upgrade Decisions and Redundant Upgrade Architecture, will begin to detail the technical components faced by the DBAs and Developers during the Upgrade process. The technical components detail the Critical Upgrade Decisions related to ANSI NULLS, Quoted Identifiers and other items. In addition, a valuable Redundant Upgrade Architecture is introduced for the Upgrade to prevent a significant set of problems. The combination of the Upgrade decisions and the Redundant Upgrade Architecture can easily make or break the upgrade for your business. Needless to say, these items require fore thought at the inception of the project by the technical staff to prevent management’s biggest fear: no available platform following the upgrade. Click
Here for the article. |
|||||||||||||
|
|||||||||||||
Large projects definitely need time up-front to define the work at the level of detail required for the project to begin. If you do not adequately define a small or medium project, the consequences will probably not be too drastic. Even if your project is estimated to take 500 hours of effort, and it takes twice as long to complete the work, it still won’t be catastrophic for your company. However, you don’t have that same luxury in a large project. For instance, if you estimate the work at 10,000 hours based on an inadequate definition process, and the actual project takes 20,000 hours instead, the results could have a material impact on your organization and your entire company. Click Here
for tips and techniques on Defining the Work for a Large Project. |
|||||||||||||
|
|||||||||||||
Free Webcasts
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
Interactive Crossword
Puzzle: "Quotable Movies"
|
|||||||||||||
|
|||||||||||||
|
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 |
|||||||||||||
