Game Development Reference
In-Depth Information
chapter 24
Overview of Database
Access with ADO.NET
“Form follows function.”
Louis Henri Sullivan—“Lippincott's Magazine,” March, 1896
In ancient times and legends of lore, information was shepherded amongst a col-
lective of elders, magicians, storytellers, and jesters. This collective served as the
data storehouse for all that was known and catalogued in the world. This method
for data storage and retrieval resulted in an entropic fallacy of facts and events.
Technology advanced, and information started to be written down on parchment,
greatly increasing its accuracy. Data eventually started to be stored in voluminous
repositories of topics. Time passed, and the world ultimately began storing data in
the first “databases,” known as libraries. These libraries established the idea of
standardizing how data was stored and retrieved. Without standards, finding spe-
cific information would prove to be a chaotic and grueling process. The usefulness
of any data storage is proportional to the storage size and retrieval efficiency.
Hundreds of years have passed since those ancient times, and we have evolved into
an era where computers can store more information than the human brain.
Almost every application handles and stores data to some extent, whether in the
form of a database, a spreadsheet, or a flat text file. Today, developers have a
multitude of databases and persistence frameworks that can be used to store and
retrieve millions of records at lightning speed. As time passes, so do these databases
and frameworks. The latest and greatest data access technology from Microsoft is
ADO.NET, which is basically a collection of classes, methods, and attributes that are
used to facilitate the efficient communication between an application and a data
Search Nedrilad ::

Custom Search