| Revision as of 20:46, 26 October 2006 edit72.22.138.12 (talk) →Features and Abilities← Previous edit |
Latest revision as of 15:20, 1 February 2023 edit undoQwerfjkl (talk | contribs)Extended confirmed users, Page movers, Rollbackers212,880 editsm Converting {{Wikidata redirect}} to {{R with Wikidata item}}. {{Wikidata redirect}} should only be used on soft redirects.Tag: PAWS [2.1] |
| Line 1: |
Line 1: |
|
|
#REDIRECT ] |
|
{ |
|
|
|
|
|
|
|
{{Redirect category shell|1= |
|
A '''database management system''' ('''DBMS''') is a ] or ] designed to manage a ], and run operations on the data requested by numerous clients. Typical examples of DBMS use include ], ] and customer support systems. DBMSs have more recently emerged as a fairly standard part of any company ]. |
|
|
|
{{R from merge}} |
|
|
|
|
|
{{R to section}} |
|
==Description== |
|
|
|
{{R with Wikidata item}} |
|
A DBMS is a complex ] of ]s that controls the ], ] and ] of ] in a ]. A DBMS includes: |
|
|
|
}} |
|
# A ] ] to define the ] of each ] hosted in the DBMS, according to the DBMS ]. |
|
|
#*The three most common organizations are the ], ] and ] models. A database management system may provide one, two or all three methods. Inverted lists and other methods are also used. The most suitable structure depends on the application and on the transaction rate and the number of inquiries that will be made.<BR>The dominant model in use today is the ad hoc one embedded in SQL, a corruption of the relational model by violating several of its fundamental principles. Many DBMSs also support the ] ] that supports a standard way for ]s to access the DBMS. |
|
|
<!-- --> |
|
|
# ]s (fields, records and files) optimized to deal with very large amounts of data stored on a ] ] (which implies very slow access ] to ]). |
|
|
<!-- --> |
|
|
# A ] and report writer to allow users to interactively interrogate the database, analyse its data and update it according to the ] on data. |
|
|
#*It also controls the ] of the database. |
|
|
#*] prevents unauthorised users from viewing or updating the database. Using passwords, users are allowed access to the entire database or subsets of it called ''subschemas''. For example, an employee database can contain all the data about an individual employee, but one group of users may be authorized to view only payroll data, while others are allowed access to only work history and medical data. |
|
|
#*If the DBMS provides a way to interactively enter and update the database, as well as interrogate it, this capability allows for managing personal databases. However, it may not leave an audit trail of actions or provide the kinds of controls necessary in a multi-user organisation. These controls are only available when a set of application programs are customised for each data entry and updating function. |
|
|
<!-- --> |
|
|
# A ] mechanism, that ideally would guarantee the ] properties, in order to ensure ], despite ] (]), and faults (]). |
|
|
#*It also maintains the ] of the data in the database. |
|
|
#*The DBMS can maintain the integrity of the database by not allowing more than one user to update the same record at the same time. The DBMS can help prevent duplicate records via unique index constraints; for example, no two customers with the same customer numbers (key fields) can be entered into the database. See ] properties for more information (Redundancy avoidance). |
|
|
|
|
|
The DBMS accepts requests for data from the application program and instructs the ] to transfer the appropriate data. |
|
|
|
|
|
When a DBMS is used, ]s 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. |
|
|
<!-- |
|
|
A ] is made up of subjects (customers, employees, vendors, etc.) and activities (orders, payments, purchases, etc.). ] is the process of deciding how to organize these data into ] types and how the record types will relate to each other. The DBMS should mirror the organization's data structure and process transactions efficiently. |
|
|
|
|
|
this is just related to databases and databases design, not to DBMS |
|
|
--> |
|
|
|
|
|
Organizations may use one kind of DBMS for daily transaction processing and 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. |
|
|
|
|
|
]s are specially designed computers that hold the actual databases and run only the DBMS and related software. Database servers are usually ] computers, with ] disk arrays used for stable storage. Connected to one or more servers via a high-speed channel, hardware ]s are also used in large volume transaction processing environments. |
|
|
|
|
|
DBMS's are found at the heart of most ]s. Sometimes DBMSs are built around a private ] ] with built-in ] support although nowadays these functions are left to the ]. |
|
|
|
|
|
==Features and Abilities== |
|
|
|
|
|
One can characterize a DBMS as an "attribute management system" where attributes are small chunks of information that describe something. For example, "color" is an attribute of a car. The value of the attribute may be a color such as "red", "blue", "silver", etc. Lately databases have been modified to accept large or unstructured (pre-digested or pre-categorized) information as well such as images and text documents. However, the main focus is still on descriptive attributes. |
|
|
|
|
|
DBMS roll together frequently-needed services or features of attribute management. This allows one to get powerful functionality "out of the box" rather than program each from scratch or add and integrate them incrementally. Such features include: |
|
|
|
|
|
* ' |
|
|
|
|
|
==History== |
|
|
|
|
|
Databases have been in use since the earliest days of electronic computing. Unlike modern systems which can be applied to widely different databases and needs, the vast majority of older systems were tightly linked to the custom databases in order to gain speed at the expense of flexibility. Originally DBMSs was found only in large organizations with the ] hardware needed to support large data sets. |
|
|
|
|
|
== |
|