Difference between centralised & client server database?

This is a discussion on Difference between centralised & client server database? within the A Brief History of Cprogramming.com forums, part of the Community Boards category; I have to write this essay type thing and part of it wants me to explain:
The differences between centralised, ...

Centralized means the data is in one place. Client server just means the clients are in a different place than the data. The statement above is worded poorly, but perhaps they mean the difference between local database and client/server. (?)

Yeah, thats kind of the impression I got. That maybe a centralised database meant users had access on a LAN only; not the net. However they would still both be centralised so its a little confusing. Still, I think I may as well go with that idea.

A centralized database system is the traditional database schema in which the database at located in one place. It is not to say the database may not be distributed among several servers, mind you. It simply means the database is considered one unit managed by one DBMS in one location and to which clients connect.

A distributed database configuration is achieved when there are several database servers replicating (or not) information between themselves and each with its own DBMS to which clients connect. Many companies starting at a given size now operate in this model. Branches or small offices hold their own - usually - stripped down version of the main database and data is usually replicated through scheduling.

Mind you that it is irrelevant how these databases are connected. WAN, LAN, Internet, is all the same.

I have no idea what a client-server database configuration is. Only thing I can think of is the client being some sort of filter through which requests to and from the database are passed. In that sense, users would connect to the client and not directly to the DBMS.

Centralized database.
I guess the old-fashioned mainframe solution would classify as centralized database - that is, you have one large computer to which you connect a large(ish) number of terminals. Everyone is working directly on the machine that holds the database, and the data never really leaves the mainframe machine [it gets displayed on a terminal, which is directly connected to the mainframe].

Client/Server database.
Client/Server DB system relies [traditionally] on a single database-server, which passes information to a client machine, where some of the data processing is done [e.g. verifying data-input, formatting data to be displayed/printed]. This reduces the load on the database server machine, as it doesn't need to perform any processing other than giving out and receiving data.

Distributed database.
Takes the client/server concept one step further by keeping multiple databases, where each database serves a set of clients. Generally, keeping the different databases in sync is one of the challenges here. The benefit is that the database can be (more) "local" to the user.

I guess the old-fashioned mainframe solution would classify as centralized database - that is, you have one large computer to which you connect a large(ish) number of terminals. Everyone is working directly on the machine that holds the database, and the data never really leaves the mainframe machine [it gets displayed on a terminal, which is directly connected to the mainframe].

Mind you, while true, other models also classify as centralized DBMSes. Namely:

Yes, they are. But the term "client-server" doesn't apply to a DBMS to define its physical organization (as does centralized and distributed). It instead defines the DBMS access configuration. So the author of that question either means something completely new to me, or didn't formulate the question correctly.

Yes, they are. But the term "client-server" doesn't apply to a DBMS to define its physical organization (as does centralized and distributed). It instead defines the DBMS access configuration. So the author of that question either means something completely new to me, or didn't formulate the question correctly.

So you don't think my three definitions are what the original poster's question refers to?

I disagree with your first two definitions as well. Any model with a centralized data source can be a centralized database (even with remote clients). Also, nothing about the client server model dictates that data must be centralized.

Centralized v.s. distributed is one issue. Client/server is totally orthogonal which makes the meaning of the sentence in the initial post difficult to understand.