Knowledge (XXG)

Centralized database

Source 📝

359: 374: 32:, or a mainframe computer. In most cases, a centralized database would be used by an organization (e.g. a business company) or an institution (e.g. a university.) Users access a centralized database through a computer network which is able to give them access to the central CPU, which in turn maintains to the database itself. 40:
The need for databases rose in the 60's with the invention of direct access storage, which allowed users to directly access records. Previously, computer systems were tape based, meaning records could only be accessed sequentially. Organizations quickly adopted databases for storage and retrieval of
153:
Centralized databases store data on a single CPU bound to a single certain physical/geographical location. Distributed databases, however, rely on a central DBMS which manages all its different storage devices remotely, as it is not necessary for them to be kept in the same physical and/or
157:
As outlined above, centralized databases are easier to maintain up to date than distributed databases. This is so because distributed databases require additional (often manual) work to keep the data stored relevant, and to avoid data redundancy, as well as to improve the overall
126:
The underlying idea of centralized databases is that they should be able to receive, maintain, and complete every single request that the main system must perform by themselves. There is only one database file, kept at a single location on a given network.
161:
If data is lost in a centralized system, retrieving it would be much harder. If, however, data is lost in a distributed system, retrieving it would be very easy, because there is always a copy of the data in a different location of the
67:
is minimized, as the single storing place of all the data also implies that a given set of data only has one primary record. This aids in the maintaining of data as accurate and as consistent as possible and enhances data
165:
Designing a centralized database is generally much less complex than designing a distributed database, as distributed database systems are based on a hierarchical structure.
146:
and duplication within its multiple sub-databases in order to maintain its records up to date. It is composed of multiple database files, all controlled by a central DBMS.
149:
The main differences between centralized and distributed databases arise due to their respective basic characteristics. Differences include but are not limited to:
28:
that is located, stored, and maintained in a single location. This location is most often a central computer or database system, for example a desktop or server
41:
data. The traditional approach for storing data was to use a centralized database, and users would query the data from various points over a network.
445: 134:, however, is a database in which all the information is stored on multiple physical locations. Distributed databases are divided into two groups: 446:"Q. What are differences in Centralized and Distributed Database Systems? List the relative advantages of data distribution? - Solved Assignments" 407: 334: 296: 260: 227: 220:
Information technology for management: driving digital transformation to increase local and global performance, growth and sustainability
108:
The central computer is a single point of failure, if the computer experiences downtime, users will not be able to access any data.
45: 56:
Centralized databases hold a substantial amount of advantages against other types of databases. Some of them are listed below:
139: 476: 111:
If there is no fault-tolerant setup and hardware failure occurs, all the data within the database will be lost.
143: 79: 29: 449: 190: 180: 135: 131: 431: 101:
Centralized databases also have a certain amount of limitations, such as those described below:
413: 403: 340: 330: 302: 292: 266: 256: 233: 223: 185: 75: 85:
Data kept in the same location is easier to be changed, re-organized, mirrored, or analyzed
64: 195: 60: 470: 117:
Difficult to scale as the centralized computer would need to be replaced to scale up.
114:
If someone accesses the central computer, all of the data can easily be compromised.
237: 417: 344: 306: 270: 71:
Central host computer can be more easily protected from unauthorized access.
175: 25: 358:
Iacob, Nicoleta Magdalena; Moise, Mirela Liliana (December 2015).
89: 44:
An example for a centralized database could be given with the
398:
Silberschatz, Abraham; Henry F. Korth; S. Sudarshan (2011).
88:
Transactions can more easily comply with the properties of
218:
Turban, Efraim; Carol Pollard; Gregory R. Wood (2021).
327:
Fundamentals of relational database management systems
48:, which centralized their databases in the mid 1970s. 289:
Concise guide to databases: a practical introduction
360:"Centralized vs. Distributed Databases. Case Study" 122:Centralized databases vs. Distributed databases 255:. Armonk, N.Y.: M.E. Sharpe. pp. 96–97. 8: 402:(Sixth ed.). New York: McGraw-Hill. 105:Access speed is limited by network speed. 207: 7: 367:Academic Journal of Economic Studies 329:. S. Esakkirajan. Berlin: Springer. 320: 318: 316: 282: 280: 213: 211: 14: 222:(Twelfth ed.). p. 71. 46:Australian Department of Defense 253:International business research 251:Neelankavil, James P. (2007). 1: 493: 400:Database system concepts 80:database administration 20:(sometimes abbreviated 154:geographical location. 191:Centralized computing 325:Sumathi, S. (2007). 287:Lake, Peter (2013). 181:Distributed database 132:distributed database 18:centralized database 373:(4). Archived from 477:Types of databases 36:Historical context 409:978-0-07-352332-3 336:978-3-540-48399-1 298:978-1-4471-5601-7 291:. Paul Crowther. 262:978-1-317-42545-8 229:978-1-119-70290-0 186:Parallel database 74:Generally easier 63:is maximized and 484: 461: 460: 458: 457: 448:. Archived from 442: 436: 435: 428: 422: 421: 395: 389: 388: 386: 385: 379: 364: 355: 349: 348: 322: 311: 310: 284: 275: 274: 248: 242: 241: 215: 76:data portability 492: 491: 487: 486: 485: 483: 482: 481: 467: 466: 465: 464: 455: 453: 444: 443: 439: 430: 429: 425: 410: 397: 396: 392: 383: 381: 377: 362: 357: 356: 352: 337: 324: 323: 314: 299: 286: 285: 278: 263: 250: 249: 245: 230: 217: 216: 209: 204: 172: 142:. It relies on 124: 99: 65:data redundancy 54: 38: 12: 11: 5: 490: 488: 480: 479: 469: 468: 463: 462: 437: 423: 408: 390: 350: 335: 312: 297: 276: 261: 243: 228: 206: 205: 203: 200: 199: 198: 196:Centralization 193: 188: 183: 178: 171: 168: 167: 166: 163: 159: 155: 123: 120: 119: 118: 115: 112: 109: 106: 98: 95: 94: 93: 86: 83: 72: 69: 61:Data integrity 53: 50: 37: 34: 13: 10: 9: 6: 4: 3: 2: 489: 478: 475: 474: 472: 452:on 2023-05-02 451: 447: 441: 438: 433: 427: 424: 419: 415: 411: 405: 401: 394: 391: 380:on 2022-11-23 376: 372: 368: 361: 354: 351: 346: 342: 338: 332: 328: 321: 319: 317: 313: 308: 304: 300: 294: 290: 283: 281: 277: 272: 268: 264: 258: 254: 247: 244: 239: 235: 231: 225: 221: 214: 212: 208: 201: 197: 194: 192: 189: 187: 184: 182: 179: 177: 174: 173: 169: 164: 160: 156: 152: 151: 150: 147: 145: 141: 140:heterogeneous 137: 133: 128: 121: 116: 113: 110: 107: 104: 103: 102: 97:Disadvantages 96: 91: 87: 84: 81: 77: 73: 70: 66: 62: 59: 58: 57: 51: 49: 47: 42: 35: 33: 31: 27: 23: 19: 454:. Retrieved 450:the original 440: 432:"Wikispaces" 426: 399: 393: 382:. Retrieved 375:the original 370: 366: 353: 326: 288: 252: 246: 219: 158:performance. 148: 129: 125: 100: 68:reliability. 55: 43: 39: 21: 17: 15: 144:replication 136:homogeneous 456:2014-10-29 384:2022-11-23 238:1333952841 202:References 52:Advantages 418:436031093 345:184984668 307:868889675 271:647515744 162:database. 471:Category 176:Database 170:See also 26:database 24:) is a 416:  406:  343:  333:  305:  295:  269:  259:  236:  226:  378:(PDF) 363:(PDF) 414:OCLC 404:ISBN 341:OCLC 331:ISBN 303:OCLC 293:ISBN 267:OCLC 257:ISBN 234:OCLC 224:ISBN 138:and 90:ACID 78:and 30:CPU 22:CDB 473:: 412:. 369:. 365:. 339:. 315:^ 301:. 279:^ 265:. 232:. 210:^ 130:A 16:A 459:. 434:. 420:. 387:. 371:1 347:. 309:. 273:. 240:. 92:. 82:.

Index

database
CPU
Australian Department of Defense
Data integrity
data redundancy
data portability
database administration
ACID
distributed database
homogeneous
heterogeneous
replication
Database
Distributed database
Parallel database
Centralized computing
Centralization


ISBN
978-1-119-70290-0
OCLC
1333952841
ISBN
978-1-317-42545-8
OCLC
647515744


ISBN

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.