 | This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Database server" – news ·newspapers ·books ·scholar ·JSTOR(September 2014) (Learn how and when to remove this message) |
Adatabase server is a server which uses adatabase application that providesdatabase services to other computer programs or tocomputers, as defined by theclient–servermodel.[citation needed][1][2]Database management systems (DBMSs) frequently provide database-server functionality, and some database management systems (such asMySQL) rely exclusively on the client–server model for database access (while others, likeSQLite, are meant for use as anembedded database).
Users access a database server either through a "front end" running on the user's computer – which displays requested data – or through the "back end", which runs on the server and handles tasks such as data analysis and storage.
In amaster–slave model, database master servers are central and primary locations of data while database slave servers are synchronized backups of the master acting asproxies.
Most database applications respond to aquery language. Each database understands its query language and converts each submitted query to server-readable form and executes it to retrieve results.
Examples of proprietary database applications includeOracle,IBM Db2,Informix, andMicrosoft SQL Server. Examples offree software database applications includePostgreSQL; and under theGNU General Public Licence includeIngres andMySQL. Every server uses its own query logic and structure. TheSQL (Structured Query Language) query language is more or less the same on allrelational database applications.
For clarification, a database server is simply a server that maintains services related to clients via database applications.
DB-Engines lists over 300 DBMSs in its ranking.[3]
The foundations for modeling large sets of data were first introduced byCharles Bachman in 1969.[4] Bachman introducedData Structure Diagrams (DSDs) as a means to graphically represent data. DSDs provided a means to represent the relationships between different data entities. In 1970,Codd introduced the concept that users of a database should be ignorant of the "inner workings" of the database.[4] Codd proposed the "relational view" of data which later evolved into theRelational Model which most databases use today. In 1971, the Database Task Report Group ofCODASYL (the driving force behind the development of the programming languageCOBOL) first proposed a "data description language for describing a database, a data description language for describing that part of the data base known to a program, and a data manipulation language."[4] Most of the research and development of databases focused on the relational model during the 1970s.
Core Concepts and OperationA database and a server are distinct things A server is a networked computer (hardware or software) that manages resources, while a database is the structured collection of data stored within it. The "database server" is the specific software and/or hardware dedicated to running the database management system (DBMS).Users don't typically connect directly Most end-users interact with a front-end application (like a website or mobile app) which, in turn, communicates with the database server on their behalf.SQL is only a part of the picture SQL is the standard language for querying and manipulating data in relational databases, but by itself, it's virtually useless. It needs to be integrated within a broader application ecosystem (middleware, reporting tools, etc.) to provide actual functionality.Performance is often CPU-bound, not I/O-bound A well-tuned database spends most of its time processing data in memory (RAM), not waiting for data to be read from disks. If a database is I/O-bound (slow disk access), it often indicates a schema problem or poor query optimization."Serverless" databases still run on servers The term "serverless" in the context of cloud databases means the user doesn't have to manage the underlying physical infrastructure; the cloud provider handles the scaling and maintenance automatically, but physical servers are still doing the work.
In 1975, Bachman demonstrated how the relational model and the data structure set were similar and "congruent" ways of structuring data while working forHoneywell.[4] Theentity–relationship model was first proposed in its current form byPeter Chen in 1976 while he was conducting research atMIT.[5] This model became the most frequently used model to describe relational databases. Chen was able to propose a model that was superior to the navigational model and was more applicable to the "real world" than the relational model proposed by Codd.[4]
