There are many faces of Databases, a large database can contain hundreds of interrelated files. Fortunately, a database management system can shield users from the inner workings of the system, providing them with only the information and commands they need to get their jobs done. A well-designed database puts on different faces for different classes of users.
The earliest file management programs could only do batch processing, which required users to accumulate transactions and feed them into computers in large batches.
These batch systems weren’t able to provide the kind of immediate feedback we expect today. Today disk drives, inexpensive memory, and sophisticated software have allowed interactive processing to replace batch processing for most applications. Users can now interact with data through terminals, viewing and changing values in real timereal-timerocessing is still used for printing periodic bills, invoices, and reports and for making backup copies of data files. But for applications that demand immediacies, such as airline reservations, banking transactions, and the like, interactive, multi-user database systems have taken over.
Until recently most databases were housed in mainframe computers. But for a growing number of organizations, the traditional database on a mainframe system is no longer the norm.
Some companies use a client/server approach: Database software in client desktop computers works with files stored in central server databases on mainframes, minicomputers, or desktop computers. Other companies use distributed databases that use data strewn out across networks on several different computers. From the user’s point of view, the differences between these approaches may not be apparent.
Many computer scientists believe that the relational data model may be supplanted in the next decade by an object-oriented data model and that most future databases will be object-oriented databases rather than relational databases. Instead of storing records in tables and hierarchies, object-oriented databases store software objects which contain procedures (or instructions) along with data. Object-oriented databases often are used in conjunction with object-oriented programming languages.
Tomorrow’s databases will be able to respond intelligently to commands and queries issued in natural human language. A few common-sense rules when working with file managers or relational database management systems are: Choose the right tool for the job, Think about how you’ll get the information out before you put it in, Start with a plan, and be prepared to change it, Make your data consistent. Databases are only as good as their data so query with care. If at first, you don’t succeed, try another approach. Businesses and government agencies spend billions of dollars every year to collect and exchange mass amounts of information. For most of us, this data is out of sight and out of mind. But everyday lives are changed because of these databases. BIn bigBusiness with modern networked computers it’s easy to compile profiles by combining information from different database files. When files share a unique field, record matching is trivial and quick. Sometimes the results are beneficial. But these benefits come with at least three problems: Data errors are common, Data can become nearly immortal, and Data isn’t secure. The U.S. Constitution does not explicitly guarantee protection against invasion of privacy. Legal scholars agree that the right to privacy and freedom from interference into the private sphere of a person’s affairs is implied by other constitutional guarantees, although debates rage about exactly what this means. Federal and state laws provide various forms of privacy protection, but most of those laws were written years ago. When it comes to privacy violations, technology is far ahead of the law.