|
June, 2003
In
This Issue
|
|
All articles have been reprinted with the written consent of their respective authors. | |||||||||||||
|
|||||||||||||
|
Displaying Tablespace Usage with a
Graph The ts_used.sql displays the total space and allocated space for all of the tablespaces in a database. The output includes a bar graph representing the percentage full for each tablespace, and also displays which tablespaces are offline. Click Here
for the script. |
|||||||||||||
|
|||||||||||||
| More
Examples of Interpreting Wait Events to Boost System Performance Part 2: Collecting Wait Event Information 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, we will explain 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. Click Here for the article. Sharing Oracle 9iAS Experiences !!! This paper aims to provide a background of our systems, and share some of our experiences with the Oracle 9iAS product. Note that this paper is not intended to fully describe the Oracle 9iAS product. Click Here
for the article. |
|||||||||||||
|
|||||||||||||
|
"Automatic Configuration for
IBM DB2 Universal Database" This paper describes the DB2 Performance Configuration Wizard, an expert tool for the configuration of DB2 Universal Databases. This utility has shown dramatic results for tuning and configuring DB2 servers on UNIX and Windows platforms, particularly on OLTP (transactional) systems. The recognition of the essential need for administration and design tools has spurred renewed interest among leading RDBMS vendors. The recent proliferation of papers on index and materialized view (summary table) selection, and the development of industrial applications in this regard by leading vendors, such as Microsoft, IBM, and Oracle, as well as numerous third party administration tools vendors, are all testament to the growing corporate recognition of this important area of investigation. The DB2 Performance Configuration Wizard is a key feature in DB2's self-managing technology portfolio. This paper discusses the purpose and features of this expert tool. Experimental results are presented along with some of the interface specifics. Click
Here for the paper. |
|||||||||||||
|
|||||||||||||
|
Trapping DTS errors
with Transact-SQL I've often been asked what the "best" method is for trapping DTS errors. This is a very broad question. What errors you care about capturing can differ from project to project, and package to package. Do you want to capture runtime errors (such as a "divide by zero" or OLE DB connection error timeouts) or logical errors (a table was empty and shouldn't be, or a flag was set to "N" but needs to be "Y")? In this article, I will address how to capture runtime errors (not logical errors) by using Transact-SQL. Transact-SQL allows us to get more control about what data we capture, present, and keep. Click
Here for the article. |
|||||||||||||
|
|||||||||||||
Goals ands objectives are statements that describe what the project will accomplish, or the business value the project will achieve. Goals are high level statements that provide overall context for what the project is trying to achieve, and should align to business goals. Objectives are lower level statements that describe the specific, tangible products and deliverables that the project will deliver. The definition of goals and objectives is more of an art than a science, and it can be difficult to define them and align them correctly. Click Here
for tips and techniques on Project Goals and Objectives. |
|||||||||||||
|
|||||||||||||
Free Webcasts
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
Interactive Crossword
Puzzle: "Famous Fathers"
|
|||||||||||||
|
|||||||||||||
|
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 send a note to unsubscribe@quest-pipelines.com and we will make every effort to remove you from our list. 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 |
|||||||||||||
