Database server - Revision history

~2025-37653-06 at 04:59, 2 December 2025

2025-12-02T04:59:12Z

← Previous revision		Revision as of 04:59, 2 December 2025
Line 13:		Line 13:
	For clarification, a database server is simply a server that maintains services related to clients via database applications.		For clarification, a database server is simply a server that maintains services related to clients via database applications.

	[[DB-Engines ranking\|DB-Engines]] lists over 300 DBMSs in its ranking.<ref>		[[DB-Engines ranking\|DB-Engines]] lists over 300 DBMSs in its ranking.<ref>{{cite web
	{{cite web
	\|url= http://db-engines.com/en/ranking		\|url= http://db-engines.com/en/ranking
	\|title= DB-Engines Ranking		\|title= DB-Engines Ranking
	\|publisher= DB-Engines.com		\|publisher= DB-Engines.com
	\|date= 2018-01-23		\|date= 2018-01-23
	\|access-date= 2018-01-23		\|access-date= 2018-01-23
	}}		\|archive-date= 2020-02-21
	</ref>		\|archive-url= https://web.archive.org/web/20200221093447/https://db-engines.com/en/ranking
			\|url-status= dead
			}}</ref>

	== History ==		== History ==
	The foundations for modeling large sets of data were first introduced by [[Charles Bachman]] in 1969.<ref name="dbhist">{{Cite web \|url=http://knol.google.com/k/databases-history-early-development \|title=Databases - History & Early Development \|access-date=2016-07-08 \|archive-url=https://web.archive.org/web/20120420063339/http://knol.google.com/k/databases-history-early-development \|archive-date=2012-04-20 \|url-status=dead }}</ref> Bachman introduced [[Data structure diagram\|Data Structure Diagrams (DSDs)]] as a means to graphically represent data. DSDs provided a means to represent the relationships between different data entities. In 1970, [[Edgar F. Codd\|Codd]] introduced the concept that users of a database should be ignorant of the "inner workings" of the database.<ref name="dbhist"/> Codd proposed the "relational view" of data which later evolved into the [[Relational Model]] which most databases use today. In 1971, the Database Task Report Group of [[CODASYL]] (the driving force behind the development of the programming language [[COBOL]]) 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."<ref name="dbhist"/> Most of the research and development of databases focused on the relational model during the 1970s.		The foundations for modeling large sets of data were first introduced by [[Charles Bachman]] in 1969.<ref name="dbhist">{{Cite web \|url=http://knol.google.com/k/databases-history-early-development \|title=Databases - History & Early Development \|access-date=2016-07-08 \|archive-url=https://web.archive.org/web/20120420063339/http://knol.google.com/k/databases-history-early-development \|archive-date=2012-04-20 \|url-status=dead }}</ref> Bachman introduced [[Data structure diagram\|Data Structure Diagrams (DSDs)]] as a means to graphically represent data. DSDs provided a means to represent the relationships between different data entities. In 1970, [[Edgar F. Codd\|Codd]] introduced the concept that users of a database should be ignorant of the "inner workings" of the database.<ref name="dbhist"/> Codd proposed the "relational view" of data which later evolved into the [[Relational Model]] which most databases use today. In 1971, the Database Task Report Group of [[CODASYL]] (the driving force behind the development of the programming language [[COBOL]]) 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."<ref name="dbhist"/> Most of the research and development of databases focused on the relational model during the 1970s.

	In 1975, Bachman demonstrated how the relational model and the data structure set were similar and "congruent" ways of structuring data while working for [[Honeywell]].<ref name="dbhist"/> The [[entity–relationship model]] was first proposed in its current form by [[Peter Chen]] in 1976 while he was conducting research at [[MIT]].<ref>[~~http~~://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.123.1085 The Entity-Relationship Model: Toward a Unified View of Data (1976)]</ref> 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.<ref name="dbhist"/>		Core Concepts and Operation
			A 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 for [[Honeywell]].<ref name="dbhist"/> The [[entity–relationship model]] was first proposed in its current form by [[Peter Chen]] in 1976 while he was conducting research at [[MIT]].<ref>[https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.123.1085 The Entity-Relationship Model: Toward a Unified View of Data (1976)]</ref> 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.<ref name="dbhist"/>

	== See also ==		== See also ==

imported>Citation bot: Add: date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 107/1152

2023-08-17T11:55:23Z

Add: date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 107/1152

New page

{{short description|Computer server providing database services}}
{{more citations needed|date=September 2014}}
A '''database server''' is a server which uses a [[database application]] that provides [[database]] services to other computer programs or to [[computer]]s, as defined by the [[client–server]] [[software modeling|model]].{{citation needed|date=January 2018|reason=The original data in this sentence was not cited and was incorrect. A database server is not a computer application. It is a server which house a database application. Web Link=https://www.pcmag.com/encyclopedia/term/40885/database-server}}<ref>{{Cite web|url=https://www.pcmag.com/encyclopedia/term/40885/database-server|title=database server Definition from PC Magazine Encyclopedia|website=www.pcmag.com|language=en|access-date=2018-02-03}}</ref><ref>{{Cite web|url=http://ecomputernotes.com/fundamental/what-is-a-database/what-is-a-database-server|title=What is a Database Server|last=Thakur|first=Dinesh|website=ecomputernotes.com|date=23 January 2013 |language=en-gb|access-date=2018-02-03}}</ref> [[Database|Database management systems]] (DBMSs) frequently provide database-server functionality, and some database management systems (such as [[MySQL]]) rely exclusively on the client–server model for database access (while others, like [[SQLite]], are meant for use as an [[embedded database]]).

Users access a database server either through a "[[Front and back ends|front end]]" running on the user's computer{{snd}}which displays requested data{{snd}}or through the "[[Front and back ends|back end]]", which runs on the server and handles tasks such as data analysis and storage.

In a [[master/slave (technology)|master–slave]] model, database master servers are central and primary locations of data while database slave servers are synchronized backups of the master acting as [[proxy server|proxies]].

Most database applications respond to a [[query 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 include [[Oracle Database|Oracle]], [[IBM Db2]], [[Informix]], and [[Microsoft SQL Server]]. Examples of [[free software]] database applications include [[PostgreSQL]]; and under the [[GNU General Public Licence]] include [[Ingres (database)|Ingres]] and [[MySQL]]. Every server uses its own query logic and structure. The [[SQL]] (Structured Query Language) query language is more or less the same on all [[relational database]] applications.

For clarification, a database server is simply a server that maintains services related to clients via database applications.

[[DB-Engines ranking|DB-Engines]] lists over 300 DBMSs in its ranking.<ref>
{{cite web
|url= http://db-engines.com/en/ranking
|title= DB-Engines Ranking
|publisher= DB-Engines.com
|date= 2018-01-23
|access-date= 2018-01-23
}}
</ref>

== History ==
The foundations for modeling large sets of data were first introduced by [[Charles Bachman]] in 1969.<ref name="dbhist">{{Cite web |url=http://knol.google.com/k/databases-history-early-development |title=Databases - History & Early Development |access-date=2016-07-08 |archive-url=https://web.archive.org/web/20120420063339/http://knol.google.com/k/databases-history-early-development |archive-date=2012-04-20 |url-status=dead }}</ref> Bachman introduced [[Data structure diagram|Data Structure Diagrams (DSDs)]] as a means to graphically represent data. DSDs provided a means to represent the relationships between different data entities. In 1970, [[Edgar F. Codd|Codd]] introduced the concept that users of a database should be ignorant of the "inner workings" of the database.<ref name="dbhist"/> Codd proposed the "relational view" of data which later evolved into the [[Relational Model]] which most databases use today. In 1971, the Database Task Report Group of [[CODASYL]] (the driving force behind the development of the programming language [[COBOL]]) 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."<ref name="dbhist"/> Most of the research and development of databases focused on the relational model during the 1970s.

In 1975, Bachman demonstrated how the relational model and the data structure set were similar and "congruent" ways of structuring data while working for [[Honeywell]].<ref name="dbhist"/> The [[entity–relationship model]] was first proposed in its current form by [[Peter Chen]] in 1976 while he was conducting research at [[MIT]].<ref>[http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.123.1085 The Entity-Relationship Model: Toward a Unified View of Data (1976)]</ref> 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.<ref name="dbhist"/>

== See also ==
* [[Replication (computer science)#Database replication|Database replication]]

== References ==
{{Reflist}}

{{Database}}

[[Category:Database servers| ]]
[[Category:Data management]]
[[Category:Servers (computing)]]