Home » , , » Download PDF MySQL™ Bible by Steve Suehring

Download PDF MySQL™ Bible by Steve Suehring


The telephone company that owns my area stores basic information about me—first and last name, address, city, state, ZIP code, and telephone number—information that’s not only basic but also common across almost all customer databases. Beyond the basic information, the local telephone company also requires my social security number (which helps them find me should I attempt to forego payment and leave the area).
Within the telephone company database is a system to keep notes and correspondence. For example, each time I call to talk with a customer service representative, a note goes into my file—indicating what I was calling about, the outcome (if any), as well as the date, time, and representative’s name—all of which is recorded automatically when the note is entered.
Beyond the personal information and correspondence notes, the telephone company database also serves as a billing system that generates my phone bill automatically on the fourth day of every month. The database tracks what services I have (such as Call Waiting, Caller ID, and so forth), associates each service with a price, and tallies my bill for the month.
Having customer, billing, and rate information in a database allows the telephone company to produce reports that can pinpoint how many customers have a certain rate group, how many live in a certain area, how many have delinquent payments, and so on.
Beyond customer reports, the telephone company has become much more sophisticated in its use of the data. Previously when I would call for customer service, I would get to talk to a live person after a bit of a wait. They then improved their customer service by allowing me to punch in my 10-digit telephone number and look up my records. From there, I might eventually get to talk to a live person (if I didn’t select any of the common tasks on the voice-mail menu). The latest improvement is the use of caller identification to ask me whether I’m calling in regard to the number that I’m calling from. After more menus and prompts, I may be able to reach a live operator.
Behind the scenes during this process is a database that can look up my information when it is fed my 10-digit number. The telephone company database can then give me choices based on the current status of my account. I once had the misfortune of fraudulent charges on my telephone bill—about $650 worth. I immediately put that amount into dispute and was told to pay my normal $45 bill—but I still
ended up receiving a disconnection notice. When I called back to inquire into the
notice, I was forwarded automatically to the collections department (who, after
some discussion, handed me off to the regular customer service department). Moral: Databases can speed up only those aspects of a transaction that don’t require the use of common sense.


  1. Getting Started
  2. Relational Database Management
  3. Preparing for Installation
  4. Linux Installation
  5. Windows Installation
  6. Macintosh Installation
  7. Starting MySQL
  8. Database Concepts and Design
  9. SQL Essentials
  10. Command Line Interface (CLI)
  11. SQL According to MySQL
  12. Database and Data
  13.  Administration
  14.  Server Configurations
  15. Security
  16. Debugging and Repairing Databases
  17. Performance Tuning
  18. Development
  19. Perl Development
  20. PHP Development
  22.  Advanced Performance
  23.  Replication
  24. Integration of Internet Services
  25. NuSphere Enhanced MySQL


0 komentar:

Posting Komentar