A Database Management System
Essay by review • February 3, 2011 • Research Paper • 1,028 Words (5 Pages) • 1,842 Views
Database Management
A database management system (DBMS) is computer software designed for the purpose of managing databases. Typical examples of DBMSs include Oracle, IBM's DB2, Microsoft Access, Microsoft SQL Server, MySQL, 4th Dimension and FileMaker. DBMSs are typically used by Database administrators in the creation of Database systems.
DBMS enables the user to store, modify, and extract information from a database. There are many different types of DBMSs, ranging from small systems that run on personal computers to large systems which run on mainframes. Computerized library systems, automated teller machines, flight reservation systems, and computerized inventory systems are some of the examples of the database applications. The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data. Database software allows users, who are not programmers, the ability to pull data from a specific database, and make that data into user-friendly information.
When a DBMS is used, information systems can be changed much more easily as the organization's information requirements change. New categories of data can be added to the database without disruption to the existing system. Organizations may use one kind of DBMS for daily transaction processing then move the detail onto another computer that uses another DBMS better suited for random inquiries and analysis. Overall systems design decisions are performed by data administrators and systems analysts. Detailed database design is performed by database administrators.
Riordan Manufacturing has three operating entities...Georgia, Michigan and California...plus a joint venture in the People's Republic of China. Basically, the operating entities each have their own Finance & Accounting Systems and they provide input that is consolidated at corporate office in San Jose. The finance & accounting department (F&A) has been unable to achieve anything remotely resembling "seamless compatibility". Some F & A data is provided to corporate via data files; some data is provided via hardcopy reports and must be re-entered; some data is provided via data files but must be converted (redirected) to the proper account codes. In sales department, each member of the sales force maintains their own set of customer records using a variety of tools. Some sales team members use paper and pencil, others sales management software such as Act, and others a hybrid. Marketing, Sales, and F& A departments have their own databases and the data can not be transfer from one database to another.
Current data management system can be improved by using client/server. Client/server is the combination of three major technologies: Relational database management systems, networks, and client interfaces. Clients execute specific local tasks with local resources. Servers provide shared resources and fulfill broad tasks. Communication enables definition and completion of full work processes. Client/server is network architecture which separates a client from a server. Each instance of the client software can send requests to a server. Database software in client desktop computers works with files stored in central server databases on the mainframe.
Advantage factors of using the client/server paradigm are
* All the data are stored at the servers, so it has better security control ability. The server can control access and resource to make sure only let those permitted users access and change data.
* It is more flexible than peer to peer (P2P) paradigm, a type of network in which each workstation has equivalent capabilities and responsibilities, for updating the data or other resources.
* There are already many matured technologies designed for Client/Server paradigm which ensures security, the user-friendliness of the interface, and ease of use.
* Any element of a C/S network can be easily upgraded.
Disadvantages factors of using the client/server paradigm are
* When a large number of clients send requests to the same server at the same time, it might cause some troubles for the server. The more clients
...
...