Customer Reviews for

The Data Access Handbook: Achieving Optimal Database Application Performance and Scalability

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
Sort by: Showing 1 Customer Reviews
Page 1 of 1
  • Posted April 14, 2009

    more from this reviewer

    optimising use of a database

    Many books about relational databases go into considerable details about optimising the use. Like the way you build the tables and how they are interrelated and joined. In contrast, Goodson and Steward describe a different type of optimisation. Here there are at least 2 computers. On 1 runs your application, while on the other is the database it uses. The application talks to a database driver on its machine, and the driver makes the network conversation with the database. The book describes ways to better configure the application's use of the driver.

    The key recommendations are thus:

    Reduce the number of network connections. Network delays can be considerable, especially if the machines are far apart.

    Reduce the amount of data returned over the network by the database. Discard fields [columns] in rows that are unlikely to be needed by the user; all the more so if the fields are large, like images. If the results are large, it takes time to convert these into network packets and then to reassemble the packets on the application machine. Here the penalty is in the time taken on the database server to find the results, the time to transmit these, and the time to reassemble them on your machine.

    There are more recommendations, but the 2 above seem the most important. The book goes into details about the others. It also has a useful chapter towards the end where several scenarios of actual non-optimal situations are given, along with the causes and resolutions. Worth careful reading for you to get inspiration and possibly clues about your situation.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews
Page 1 of 1