Practical Oracle8i: Building Efficient Databases / Edition 1

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (23) from $1.99   
  • New (5) from $30.00   
  • Used (18) from $1.99   

Overview

What is really involved in building effective Oracle database systems, and how do you approach the endeavor in a way that increases your chances for success?

Practical Oracle8i™ offers a real-life approach to constructing Oracle databases--one that is geared toward solving important business problems. This book will help you devise appropriate strategies for database design that takes into account Oracle's technical underpinnings, hardware and user limitations, and tradeoffs between simplicity and efficiency. It discusses selecting the Oracle features needed to perform specific functions and demonstrates how to structure code most effectively for the features being implemented.

Practical Oracle8i™ presents an overview of Oracle that clearly explains the central functions that are key to Oracle's operation. In addition, the book presents the fundamentals of the system, covering the way in which data is stored, packed, and made visible, as well as the dynamic features involved in transactions and calculations. Specific topics covered include:

  • A discussion of why Oracle projects fail
  • Leveraging tablespaces
  • Partitioning
  • LOBs
  • Autonomous transactions
  • Row-level security for virtual private databases
  • Parallel query and parallel server
  • The new analytical functions introduced in Oracle 8.1.6

This book also provides a summary of the most useful new features of Oracle 8.1.5, practical tips for tuning performance and testing features, and information on the major space-management features of an Oracle database.

Written by one of the world's most knowledgeable and experienced Oracle database designers and programmers, Practical Oracle8i™ reveals the strategies, techniques, and insights that will enable you to understand the technology's full potential and put Oracle to work for successful database systems.

0201715848B04062001

Read More Show Less

Editorial Reviews

Booknews
This book offers a practical approach to constructing Oracle databases geared towards solving business problems. With numerous charts and tables, it presents an overview of the program, explaining the central functions and its technical underpinnings, to allow the reader to devise appropriate strategies for database design given user or hardware limitations. It also provides insight on why many Oracle projects fail, and information on leveraging tablespaces, partitioning, LOBs, row-level security and parallel queries and servers. Annotation c. Book News, Inc., Portland, OR (booknews.com)
From The Critics
Practical Oracle 8i provides an invaluable approach to constructing Oracle databases. Jonathan Lewis draws upon his mor than fifteen years experiences designed databases to provide an informative discussion of why Oracle projects fail, how to leverage tablespaces, covers the essential issues of partitioning, LOBs, autonomous transactions, row-level security for virtual private databases, parallel query and parallel server, as well as the new analytical functions introduced in Oracle 8.1.6. Of special interest are the useful and practical tips for tuning performance and testing features, as well as information on the major space-management features of an Oracle database. Practical Oracle8i is definitive and very highly recommended reading for anyone developing or working with database technology in general, and an Oracle database in particular.
Read More Show Less

Product Details

  • ISBN-13: 9780201715842
  • Publisher: Addison-Wesley
  • Publication date: 12/18/2000
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 672
  • Product dimensions: 7.40 (w) x 9.05 (h) x 1.33 (d)

Meet the Author

Jonathan Lewis is a leading independent database consultant with over fifteen years' experience helping clients design and implement Oracle database systems. Much of his career has been spent working around the problems caused by the inappropriate use of the technology. In addition, he is the Director for Products and Services for the UK Oracle Users Group and maintains a Web site of Oracle tips and advice.

0201715848AB04062001

Read More Show Less

Read an Excerpt

Why Another Book?

Since there are so many books about Oracle already on the market, why have I bothered to sit down and add to the pile? In the age of Internet news groups and Web sites, it isn't for the fame. And given the specialized nature and likely circulation of such a tome, it probably isn't for the fortune.

Every now and again, usually while I've been rattling on enthusiastically about some obscure and esoteric feature of the way in which Oracle works, I've been asked, Why don't you write a book about Oracle since you know so much about it? My answer has always been the same: If you write a technical book about Oracle, it will be out of date by the time you've finished writing it, and within a year of publication it will be 20% misleading, inappropriate, or just plain wrong.

I have, however, finally given in to temptation because I've spent too long traveling around the world helping people to get the best out of their databases, and discovering time and again that the single biggest aid to success is to start well by picking the most appropriate features for the job.

This book is my attempt to tell you about some of the more useful things I have discovered while designing or fixing a few of the more thought-provoking databases that I have come across. I'm writing it partly for the challenge, and partly because I enjoy making Oracle work well and want to pass on some of the interesting and entertaining insights I have had. I hope you enjoy reading it and, more important, I hope you get a better feeling for what the Oracle database can do for you.

Who Is It For?

There are four stages to doing a job well:

  1. Knowing what can be done
  2. Knowing whether it should be done
  3. Being able to do it in theory
  4. Being able to do it in practice

Many of the books about Oracle currently on the market seem to focus on the finer points of the third and fourth steps. My aim is to help you with the first two, although this entails including practical observations relevant to the third and fourth steps.

This book does not exist to thrill the hard-core specialists by supplying subtle secrets and technical tweaks that will allow them to squeeze an extra half of a percent from their database. This book is here to help everyone get to a stage where they can put together a system that gives response times that are reasonable, considering the investment made in hardware, software, and human effort. Whether you are a manager, designer, database administrator, or programmer, there is something in this book for you. For the manager it gives a wide-ranging view of what Oracle is capable of and what you can expect your team to achieve. For the designer it outlines the possibilities offered by the many features of the relational database management system. For the database administrator it describes how using the right features correctly can make managing the database much easier. For the programmer (who is always keen to know how things really work) it makes it possible to connect the code that he writes to the features he is using, so that he can structure his code in the most appropriate way.

Which Version of Oracle?

A couple of years ago, a collection of information technology directors in the United Kingdom were asked what they perceived to be the biggest problems they had in managing their departments. Somewhere in the top ten was this response: the rate at which Oracle Corporation produces upgrades and new versions of their products. If Oracle keeps moving that fast, how do you pick a target when writing a book about it?

My strategy for tackling problems is the same regardless of the version of Oracle with which I'm working, so when you read this book you don't really have to worry about which version of Oracle you are using. However, I am going to focus as much as I can on Oracle 8.1.5—for the simple reason that it is the latest version (at least it was when I started writing).

It is also worth noting that Oracle 8.1.5 is the first "proper" release for some years to introduce many new features aimed at increasing the range of tasks that the database can handle efficiently and cost-effectively, which means, unfortunately, that it also introduces even more ways of allowing you to mix and match the wrong features.

Inevitably, between the time I started writing and the time this book was published, Oracle 8.1.6 went on general release. In that release, Oracle introduced features that it refers to as the analytic functions. The scope for reducing the programming effort and runtime workload on heavy-duty queries is so dramatic that I have felt compelled to include some details of analytic functions in Chapter 23.

What's in This Book?

Most of the books relating to Oracle seem to fall into one of three groups: the tuning guide, the enhanced manual, and the guide to relational database design. This book falls, I hope, outside all three groups. It works outward from the database engine itself and gives you some good ideas on how to use that engine to implement your application.

This book encourages you to consider just two important principles—how to think when designing an Oracle-based application, and how to ensure that you pick the most appropriate features of Oracle when implementing your system.

Whatever else it may be, though, this book is not a technical book. Or at least it's not a very technical book. I am not planning to go into any great and intricate detail about the internal workings of Oracle. (After all, I don't want the book to be out of date before it's published.) I do, however, take a little time to describe a couple of the central architectural features in some detail. I explain, in a simple way, the very small number of critical mechanisms that are key to the way in which the Oracle database engine works, and then I describe the ways in which these mechanisms can have a significant impact on how you have to design your application.

If you get to the end of this book feeling that it has made sense, then you are on track to avoid most of the traps that cause so many projects to end up overpriced, too complex, and poor performers.

What's Not in This Book?

There are a number of "value-added" modules that come with the Oracle relational database management system. In Oracle 8.1.5 these are known as the intermedia cartridges, and they are little applications that use the "extensible framework" of Oracle to add functionality for handling text, spatial data, time-based data, and visual data. These add-ons are excluded from this book.

I have also ignored the "Web-enabling" features of Oracle 8.1.5, namely the PL/SQL packages that can be called to pass data from Oracle tables to Web pages, the inclusion of Java as an internalized database language, and the Web application server itself. The Web interface is, after all, simply another way to use the database, and Java is just another programming language that can be used to address the database.

The last major omissions are advanced queuing and replication, partly because they are too wide ranging to be covered in a single chapter, and partly because they too fall into the area of the more exotic add-ons that are likely to be of less benefit to the general user.

Looking back at the last three paragraphs, I think they really sum up my approach to application design: The database is much more important than the language or tool that may be talking to it. And that, of course, is precisely why it is necessary for the designers and programmers to understand how the database works. It doesn't matter how wonderful the application is, or how high-tech the language is, or how user-friendly the interface is. If you try to make the database behave in an unsuitable fashion, then you are unlikely to come to the end of the project feeling like a winner.

The Framework of the Book

The book is designed as a series of self-contained essays. Each essay pulls together a number of threads that might otherwise be scattered across several of the Oracle manuals, and presents an entire topic in a fashion that helps you to identify the risks and rewards of using a particular feature of the software.

This means that there is a degree of repetition from time to time. For example, the chapter on partitioning mentions some details of parallel query, and the chapter on parallel query comments on its particular application to partitioned tables.

You may also find that there are apparent contradictions in some of the comments I make and advice that I give. At one point (Chapter 8) I describe the benefits of wasting space to reduce the administrative burden, but at another point (Chapter 13) I make several comments about rebuilding data objects to pack the data and save space. Sometimes such points are not as contradictory as they may at first seem. Sometimes it is simply the case that different demands on resources call for completely different strategies.

You may find that a number of technical issues are addressed in a rather more informal fashion than you might hope. My intention is to give the flavor of how Oracle works without worrying too much about the exact detail of the internal operations. If you are already a highly skilled operative fully conversant with the way Oracle works, please be patient. Many of the omissions and vagaries in the early stages of this book are deliberate.

The book is divided into three main parts:

  1. Part 1 (Chapters 1 through 4) is a very high-level view of the Oracle engine, how it should be approached, and why so many projects using Oracle fail to achieve their objectives.
  2. Part 2 (Chapters 5 through 18) approaches Oracle from the "static" viewpoint of how the data can be stored, packed, and made visible within the database.
  3. Part 3 (Chapters 19 through 24) is biased toward the "processing" side of Oracle, focusing more on the dynamic side of moving data in and around the database.

There are also four appendices:

  1. Appendix A is a brief summary of some of the more interesting features of Oracle 8.1.5. It contains a mixed collection of features that I think are useful. In some cases I have made a big fuss about a little feature; in other cases you may decide I have completely ignored a big feature. Just because I don't mention some new features doesn't mean they aren't of any use—it may simply mean that I haven't come across, or imagined, an environment in which they would have a significant impact on the quality, clarity, or performance of a project.
  2. Appendix B contains a brief description of the limited number of tuning tasks that should be adequate for most reasonably designed systems.
  3. Appendix C provides a few hints on techniques for testing the relevance of features.
  4. Appendix D contains a description of the main space management features of an Oracle database.
Read More Show Less

Table of Contents

Preface.

Why Another Book?

Who Is It For?

Which Version of Oracle?

What's in This Book?

What's Not in This Book?

The Framework of the Book.

Conventions Used in the Book.

Acknowledgments.

A Cautionary Tale.

I. OVERVIEW.

1. What Is Oracle?

Data, Undo, and Redo.

Data Change.

Uncommitted Data.

Committed Data.

Side Effects of Rollback.

Locating the Data.

Conclusion.

2. Why Do Projects Fail?

Ignoring the Technology.

Avoiding the Arithmetic.

Fudging the Prototype.

Confusing the Responsibilities.

Sharing the Database.

Conclusion.

3. How the Engine Works.

The I/O Trap.

Reading Data.

Changing Data.

Side Effects.

Conclusion.

4. Classifying Your Target.

Manual Transaction Processing.

Automatic Transaction Processing.

High Batch Throughput.

Data Warehouse.

The Internet Changes Everything.

Conclusion.

II. DATA STORAGE.

5. Making the Most of Tables.

Rebuilding the Data.

Packing the Data.

More Packing.

Dropping Columns.

Strategy.

Strategy.

Up-to-Date Statistics (Nearly).

Wide Tables.

Problems and Quirks.

Strategy Notes.

6. Basic Indexing.

B-Tree Indexing.

Updates to the Index.

Low-Level Processing.

Using the Index.

Bitmap Indexing.

Administration.

Problems and Quirks.

Strategy Notes.

7. Enhanced Indexing.

Compressed B-Trees.

Minimize Records per Block.

Descending Indexes.

Reverse Key Indexes.

Function-Based Indexes.

Built-in Functions.

User-Defined Functions.

Administration.

Rebuild.

Coalesce.

Statistics.

Rename.

Optimization.

Index Joins.

Star Transformations.

Problems and Quirks.

Strategy Notes.

8. Leveraging Tablespaces.

Tablespace Strategies.

Rollback Tablespaces.

Temporary Tablespaces.

Classification.

Locally Managed Tablespaces.

General Tablespace Management.

Transportable Tablespaces.

Tablespace Point-in-Time Recovery.

Problems and Quirks.

Strategy Notes.

9. Temporary Space.

Temporary Tablespaces.

So What's New in 8.1?

Temporary Files.

Temporary Tables.

Temporary LOBs.

Problems and Quirks.

Strategy Notes.

10. Files, Raw, and RAID.

Files or Raw.

The Management Issues.

The Performance Issue.

Archiving.

Conclusion.

RAID Levels.

RAID0.

RAID.

RAID 0/1 and RAID 1/0.

RAID.

Generic RAID.

Disk Cache.

Problems and Quirks.

Strategy Notes.

11. Views.

Basics of Views.

Views for Performance.

In-Line Views.

SORT_AREA_SIZE.

Rollover Views.

Views for Security.

Views for Functionality.

Views for Clarity.

Functions Returning Datasets.

Partition Access.

Analytical Functions and Others.

Updatable Join Views.

Simple Join Views.

In-Line Updatable Views.

Object Views.

A Farewell to Partitioned Views.

Problems and Quirks.

Strategy Notes.

12. Introducing Partitioning.

Partitioning Options.

How Does Range Partitioning Work?

How Does Hash Partitioning Work?

How Does Composite Partitioning Work?

Partitioning — General Points.

Multicolumn Partitioning.

Problems and Quirks.

Strategy Notes.

13. Using Partitioning.

Administration.

Dropping Partitions.

Tablespace Management.

Packing Tablespaces.

Data Loading.

Indexing Existing Tables.

Performance.

Range Partitions with Dates.

Hash Partitions and Composite Partitions.

Partition-wise Joins.

EXPLAINPLAN.

Statistics.

Partitions and Parallel Execution.

Problems and Quirks.

Strategy Notes.

14. Index-Organized Tables.

Basic IOTs.

Indexes on IOTs.

On-Line Moves.

Advanced IOTs.

LOBs, Varrays, and Nested Tables.

Partitioning.

Restrictions on IOT Partitions.

Problems and Quirks.

Strategy Notes.

15. Simple Objects.

Getting Started with Objects.

Objects and Relational Tables.

Object Tables.

Problems and Quirks.

Strategy Notes.

16. Collection Objects.

Varrays.

Tables.

Transient Collections.

A Cautionary Tale.

Problems and Quirks.

Strategy Notes.

17. Handling Large Objects.

Internal or External?

Why LOBs?

Working with LOBs.

Working with BFILEs.

The LOB Package — DBMS_LOB.

BFILEs.

Permanent LOBs.

Temporary LOBs.

Generic LOBs.

Problems and Quirks.

Strategy Notes.

18. Data Integrity.

Types of Constraints.

Primary Key.

Unique Key.

Foreign Key.

Check.

View.

Scope.

Partition Boundaries.

Using Constraints.

Adding Constraints.

Truncating Tables.

Loading Data.

Cascading Changes to Primary Key.

Data Warehouses and Constraints.

Triggers.

Audit Trail.

Problems and Quirks.

Strategy Notes.

III. DATA MANIPULATION.

19. PL/SQL.

What Is PL/SQL?

The Best Bits.

Native Dynamic SQL.

Array Processing.

Passing Result Sets into and out of Procedures.

Invoker Rights.

Supplied Packages.

Problems and Quirks.

Strategy Notes.

20. Autonomous Transactions.

Simple Autonomous Transactions.

Autonomous Triggers.

Sequence Numbers.

Who Is Locking My Row?

A Counter Example.

Problems and Quirks.

Strategy Notes.

21. Row-level Security.

Historic Implementations.

Security Policies.

Refining Row-level Security.

Problems and Quirks.

Strategy Notes.

22. Parallel Query and Parallel Server.

Parallel Server.

The IDLM.

PCM and Non-PCM.

PCM Locks and Data Locks.

Defining PCM Locks.

Avoiding Pinging.

Parallel Execution.

Problems and Quirks.

Parallel Server.

Parallel Query.

Strategy Notes.

Parallel Server.

Parallel Query.

23. Number Crunching.

Cube and Rollup.

Programming Solutions.

Expensive SQL.

Temporary Tables.

Enhancements in Version 8.1.5.

Rollup.

Cube.

Analytic Functions.

Miscellaneous.

Case Statements.

SAMPLE Clause.

Materialized Views.

Implementation.

Problems and Quirks.

Strategy Notes.

24. Fallback.

Choose Your Disaster.

Pick a Time Scale.

The 30-Second 100% Fail-over.

The Five-Minute 100% Fail-over.

Off-site 100% Fail-Over.

Clones at 99%.

Backups.

The Standby Database.

Recovery Manager.

Problems and Quirks.

Strategy Notes.

Appendix A: Feature Reference.

Standby Database.

Row-level Security.

Tablespace Management.

Transportable Tablespaces.

Temporary Tablespaces.

Temporary Tables.

PL/SQL.

Database Triggers.

Partitioning.

Autonomous Transactions.

Three-tier Applications.

Indexes.

LOBs.

Analytic Functions (Version 8.1.6).

LogMiner.

Replication.

Query Rewrite.

IOTs.

Integrity Constraints.

Parallel Execution.

JServer.

Appendix B: Tuning to 90%.

V$SQL — Recent SQL with Costs.

V$FILESTAT/V$TEMPSTAT.

V$SYSTEM_EVENT/V$SESSION_EVENT.

The X$ Files.

X$KCBFWAIT.

X$KSQST.

Helping the Developers.

Conclusion.

Appendix C: Testing to Destruction.

The Basis of Testing.

A Cautionary Tale.

Generating Data.

Validating the Results.

Execution Paths.

Events.

Database Dumps.

Conclusion.

Appendix D: Space Management.

The Block.

INITRANS and MAXTRANS.

PCTFREE and PCTUSED.

Choosing a Block Size.

The Extent.

The Segment.

The Tablespace.

The Disk Array.

Conclusion.

About the Author.

Index. 0201715848T04062001.

Read More Show Less

Preface

Why Another Book?

Since there are so many books about Oracle already on the market, why have I bothered to sit down and add to the pile? In the age of Internet news groups and Web sites, it isn't for the fame. And given the specialized nature and likely circulation of such a tome, it probably isn't for the fortune.

Every now and again, usually while I've been rattling on enthusiastically about some obscure and esoteric feature of the way in which Oracle works, I've been asked, Why don't you write a book about Oracle since you know so much about it? My answer has always been the same: If you write a technical book about Oracle, it will be out of date by the time you've finished writing it, and within a year of publication it will be 20% misleading, inappropriate, or just plain wrong.

I have, however, finally given in to temptation because I've spent too long traveling around the world helping people to get the best out of their databases, and discovering time and again that the single biggest aid to success is to start well by picking the most appropriate features for the job.

This book is my attempt to tell you about some of the more useful things I have discovered while designing or fixing a few of the more thought-provoking databases that I have come across. I'm writing it partly for the challenge, and partly because I enjoy making Oracle work well and want to pass on some of the interesting and entertaining insights I have had. I hope you enjoy reading it and, more important, I hope you get a better feeling for what the Oracle database can do for you.

Who Is It For?

There are four stages to doing a job well:

  1. Knowing what can be done
  2. Knowing whether it should be done
  3. Being able to do it in theory
  4. Being able to do it in practice

Many of the books about Oracle currently on the market seem to focus on the finer points of the third and fourth steps. My aim is to help you with the first two, although this entails including practical observations relevant to the third and fourth steps.

This book does not exist to thrill the hard-core specialists by supplying subtle secrets and technical tweaks that will allow them to squeeze an extra half of a percent from their database. This book is here to help everyone get to a stage where they can put together a system that gives response times that are reasonable, considering the investment made in hardware, software, and human effort. Whether you are a manager, designer, database administrator, or programmer, there is something in this book for you. For the manager it gives a wide-ranging view of what Oracle is capable of and what you can expect your team to achieve. For the designer it outlines the possibilities offered by the many features of the relational database management system. For the database administrator it describes how using the right features correctly can make managing the database much easier. For the programmer (who is always keen to know how things really work) it makes it possible to connect the code that he writes to the features he is using, so that he can structure his code in the most appropriate way.

Which Version of Oracle?

A couple of years ago, a collection of information technology directors in the United Kingdom were asked what they perceived to be the biggest problems they had in managing their departments. Somewhere in the top ten was this response: the rate at which Oracle Corporation produces upgrades and new versions of their products. If Oracle keeps moving that fast, how do you pick a target when writing a book about it?

My strategy for tackling problems is the same regardless of the version of Oracle with which I'm working, so when you read this book you don't really have to worry about which version of Oracle you are using. However, I am going to focus as much as I can on Oracle 8.1.5--for the simple reason that it is the latest version (at least it was when I started writing).

It is also worth noting that Oracle 8.1.5 is the first "proper" release for some years to introduce many new features aimed at increasing the range of tasks that the database can handle efficiently and cost-effectively, which means, unfortunately, that it also introduces even more ways of allowing you to mix and match the wrong features.

Inevitably, between the time I started writing and the time this book was published, Oracle 8.1.6 went on general release. In that release, Oracle introduced features that it refers to as the analytic functions. The scope for reducing the programming effort and runtime workload on heavy-duty queries is so dramatic that I have felt compelled to include some details of analytic functions in Chapter 23.

What's in This Book?

Most of the books relating to Oracle seem to fall into one of three groups: the tuning guide, the enhanced manual, and the guide to relational database design. This book falls, I hope, outside all three groups. It works outward from the database engine itself and gives you some good ideas on how to use that engine to implement your application.

This book encourages you to consider just two important principles--how to think when designing an Oracle-based application, and how to ensure that you pick the most appropriate features of Oracle when implementing your system.

Whatever else it may be, though, this book is not a technical book. Or at least it's not a very technical book. I am not planning to go into any great and intricate detail about the internal workings of Oracle. (After all, I don't want the book to be out of date before it's published.) I do, however, take a little time to describe a couple of the central architectural features in some detail. I explain, in a simple way, the very small number of critical mechanisms that are key to the way in which the Oracle database engine works, and then I describe the ways in which these mechanisms can have a significant impact on how you have to design your application.

If you get to the end of this book feeling that it has made sense, then you are on track to avoid most of the traps that cause so many projects to end up overpriced, too complex, and poor performers.

What's Not in This Book?

There are a number of "value-added" modules that come with the Oracle relational database management system. In Oracle 8.1.5 these are known as the intermedia cartridges, and they are little applications that use the "extensible framework" of Oracle to add functionality for handling text, spatial data, time-based data, and visual data. These add-ons are excluded from this book.

I have also ignored the "Web-enabling" features of Oracle 8.1.5, namely the PL/SQL packages that can be called to pass data from Oracle tables to Web pages, the inclusion of Java as an internalized database language, and the Web application server itself. The Web interface is, after all, simply another way to use the database, and Java is just another programming language that can be used to address the database.

The last major omissions are advanced queuing and replication, partly because they are too wide ranging to be covered in a single chapter, and partly because they too fall into the area of the more exotic add-ons that are likely to be of less benefit to the general user.

Looking back at the last three paragraphs, I think they really sum up my approach to application design: The database is much more important than the language or tool that may be talking to it. And that, of course, is precisely why it is necessary for the designers and programmers to understand how the database works. It doesn't matter how wonderful the application is, or how high-tech the language is, or how user-friendly the interface is. If you try to make the database behave in an unsuitable fashion, then you are unlikely to come to the end of the project feeling like a winner.

The Framework of the Book

The book is designed as a series of self-contained essays. Each essay pulls together a number of threads that might otherwise be scattered across several of the Oracle manuals, and presents an entire topic in a fashion that helps you to identify the risks and rewards of using a particular feature of the software.

This means that there is a degree of repetition from time to time. For example, the chapter on partitioning mentions some details of parallel query, and the chapter on parallel query comments on its particular application to partitioned tables.

You may also find that there are apparent contradictions in some of the comments I make and advice that I give. At one point (Chapter 8) I describe the benefits of wasting space to reduce the administrative burden, but at another point (Chapter 13) I make several comments about rebuilding data objects to pack the data and save space. Sometimes such points are not as contradictory as they may at first seem. Sometimes it is simply the case that different demands on resources call for completely different strategies.

You may find that a number of technical issues are addressed in a rather more informal fashion than you might hope. My intention is to give the flavor of how Oracle works without worrying too much about the exact detail of the internal operations. If you are already a highly skilled operative fully conversant with the way Oracle works, please be patient. Many of the omissions and vagaries in the early stages of this book are deliberate.

The book is divided into three main parts:

  1. Part 1 (Chapters 1 through 4) is a very high-level view of the Oracle engine, how it should be approached, and why so many projects using Oracle fail to achieve their objectives.
  2. Part 2 (Chapters 5 through 18) approaches Oracle from the "static" viewpoint of how the data can be stored, packed, and made visible within the database.
  3. Part 3 (Chapters 19 through 24) is biased toward the "processing" side of Oracle, focusing more on the dynamic side of moving data in and around the database.

There are also four appendices:

  1. Appendix A is a brief summary of some of the more interesting features of Oracle 8.1.5. It contains a mixed collection of features that I think are useful. In some cases I have made a big fuss about a little feature; in other cases you may decide I have completely ignored a big feature. Just because I don't mention some new features doesn't mean they aren't of any use--it may simply mean that I haven't come across, or imagined, an environment in which they would have a significant impact on the quality, clarity, or performance of a project.
  2. Appendix B contains a brief description of the limited number of tuning tasks that should be adequate for most reasonably designed systems.
  3. Appendix C provides a few hints on techniques for testing the relevance of features.
  4. Appendix D contains a description of the main space management features of an Oracle database.

0201715848P04062001

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)