Good morning, everyone.

So, we are the group 6 and we are here to report chapter 6 introduction to
databases. We have here our learning objectives, first is to demonstrate adequate familiarity with
database management systems or the DBMS and Use SQL or the Structure Query Language.

So, in our introduction, A database system is basically just a computerized record-keeping system.
The database itself can be regarded as a king of electronic filing cabinet; that is, it is a repository or
container for a collection of computerized data files.

Example may tatlo kang closet or cabinet, at bawat isang cabinet ay may nakalagay na mga gamit. Sa
isang cabinet pwedeng nandun lahat ng uniforms mo, then sa isang cabinet naman nakalagay yung
mga pambahay mo then sa isa is yung mga sandals or shoes mo. So, as you can see, organized yung
mga gamit mo. Same with the database, kaya tinawag siyang king of electronic filling cabinet, because
it contains collections of computerized data files. Para mas maintindihan natin kung ano nga ba itong
databse na ito, let us first define it.

So, A database is a collection of persistent data that is used by the application system of some given
enterprise. Pansin niyo na nakahighlight yung word na persistent. Ano nga ba itong persistent na
sinasabi natin.

As you can see, by persistent we mean, intuitively, that database differs in kind from other more
ephemeral data, such as input data, output data, work queues, software control blocks, SQL
statements, intermediate results and more generally any data that is transient in nature. More precisely,
masasabi natin na data persist if it is infrequently accessed and not likely to be modified. Kumbaga
once na pumasok na yung data in our database system, permanent na siya unless there is an explicit
request to the DBMS dun lang pwedeng ma alter yung data na pinasok sa system.

Another word that is highlighted in the definition of database is the word “enterprise”. The term
enterprise here is simply a convenient generic term for any reasonably self-contained commercial,
scientific, technical, or other organization. Meaning enterprise can be a single individual na ang system
eh maliit lang or it could be a corporation or large business na may malaking database. Example ng
enterprise includes, a manufacturing company, bank, hospital, university, or government department.
So sa bawat enterprise syempre madami yang data na nagegenerate or hawak.

Next is the benefits of the database approach. First on our list, the data can be shared. Sharing
means not only those existing applications can share the data in the database, but also that new
applications can be developed to operate against that same data. In other words, it might be possible to
satisfy the data requirements of new applications without having to add new data to the database.
Simply ibig sabihin, yung data is pwedeng madistribute sa maramihang users or applications pero
minemaintain pa rin yung data fidelity or yung accuracy ng data.

Second, Redundancy can be reduced. Example nito is that kunyari merong dalawang records of files
sabihin natin na yung isang file is the personnel application tapos yung isa is education record
application. So both files meron silang stored data na name, age, address etc. ganyan so para
maeliminate yung redundancy pwedeng pagsamahin ni administrator yung files. Since same sila ng
data information ganyan, as long as si administrator is aware of the data requirements ng mga files na
yun.

Third, Inconsistency can be avoided (to some extent). Diba ang sabi natin through database
approach, redundancy can be reduced or controlled, so ibig sabihin there is a guarantee that the
database is consistent. Pano ba natin maacquire itong consistent na ito? So dapat kung anong ginawa
mong pagbabago or alteration sa isang application dapat applied mo din sa isa.

Fourth, Transaction support can be provided. Diba sa computer meron siyang update na ginagawa,
so the same with the database, If the user has made two updates part of the same transaction, then the
system can effectively guarantee that either both of them are done.

Fifth, Integrity can be maintained, in database dapat pinaka importante ang integrity, because we
need to ensure that the data is correct in the database.

Next, Security can be enforced, so syempre we have different protection protocols in using database
system. We incorporate passwords to the different level of employees and also nandyan si DBA or si
Database Administrator to ensure na the only means of access to the database is through proper
channels.

Next, Conflicting requirements can be balanced, dito naman since database system is using
computer, we can ensure that the structure of the system can accommodate or provide the best service
to the enterprise or to the users.

And lastly, Standards can be enforced, the DBA can ensure that all applicable standards are
observed in the representation of the data, including any or all of the following: departmental,
installation, corporate, industry, national, and international standards.

WHAT IS A DATABASE SYSTEM?

A database system is basically a computerized record-keeping system. Ibig sabihin in the database
system we use computers, and computers overall purpose is to store information and also allow users
to retrieve and update the information on demand.

Tandaan natin that we treat the terms data and information as synonyms. Pero there are some
writers na they prefer to distinguish data from information. So sabi dito, data are individual facts and
raw form of knowledge that doesn’t carry any significance or purpose. Raw ibig sabihin kung ano yung
na generate mo from a transaction yun na yun. Yun na mismo yung data, wala ka pang any changes
na ginawa with the retrived data. Kapag naman information, eto na yung interpretation of data.

So bakit nga ba natin kailangan gamitin ang database system? Ano ba yung mga advantages nito
that we need to use it over the traditional paper-based method of record-keeping.

Una, Compactness, so in database system kasi paperless na siya so hindi mo na kailangan ng bulto-
bultong mga papel para mastore yung mga data.

Pangalawa is Speed, with database system mas mabilis mo mareretrieve yung mga needed mong
files or mas mabili yung update nung information since computerized na yung mga data.

Next, Less drudgery, dito naman diba in the traditional paper-based method of record-keeping eh
naka store lang sa cabinet yung mga files ng enterprise, so kapag database yung gamit natin, mas
malelessen yung pagod mo na mag compile ng mga files sa cabinet.

Fourth, we have Currency, So with the aid of database system, mas accurate yung information na
makukuha natin, yung available information pwedeng siyang makuha at any time.
And lastly, Protection, mas protected na yung data natin sa mga unintentional loss like, kunyari baha,
ganyan or unlawful access, kasi nga in the database approach encrypted na siya with passwords.

Let’s move forward, dito naman tayo sa database management system or the DBMS. The DBMS is a
special software system that is programmed to know which data elements each user is authorized to
access. So using the DBMS, nacocontrol natin kung sino lang ang authorized na mag access sa mga
data sa ating system. Una, si user’s program mag sesend siya ng request to access the data sa DBMS,
and then si DBMS ivavalidate niya kung authorize ba yung sender using the user’s level of authority. So
kapag, naassess ni DBMS na unauthorized yung sender, idedeny niya yung access ng sender sa mga
data in the database.

Next are the elements of the database environment. The database environment is breakdown into
four primary elements: users, the DBMS, the database administrator, and the physical database.

Users
Users access in the database can be in two ways. The first is via user application programs that
systems professional prepare. So itong program na ito, nag sesend siya ng data access request sa
DBMS, then si DBMS ivavalidate niya request. So under this mode of access, yung presence ng DBMS
is transparent to the users.

The second method of database access is via direct query, which requires no formal user programs. So
si DBMS meron siyang built in query facility, si built in query facility siya yung nag aallow sa authorized
users na mag process ng data independently of professional programmers.

The second element of the database approach is the DBMS. The DBMS provides a controlled
environment to assist (or prevent) user access to the database and to efficiently manage the data
resource. Each DBMS model accomplishes these objectives differently, but some typical features
include: Product development, back up and recovery, database usage reporting and database access.
yung database access siya yung most important feature ng DBMS kasi it permits authorized user
access to the database.

So meron tayong tatlong software modules na nagfafacilitate ng database access. We have the
data definition language. So DDL, is a programming language used to define the physical database
to the DBMS. Kasali dyan yung mga names, relationship ng lahat ng data elements, record files na
bumubuo sa database. (example: customers information). The DDL defines the database on three
levels called views: the internal view, the conceptual view (schema) and the user view (subschema).

Internal view: The internal view presents the physical arrangement of records in the database. Si
internal view siya yung lowest level of representation. Sa internal view kasi dinedescribe niya yung
structure nf records, yung mga ugnayan sa pagitan nila and the physical arrangement and sequence of
records in a file.

Conceptual view or schema: It represents the database logically and abstractly, rather than the way it
is physically stored. This view allows users’ programs to call for data without knowing or needing to
specify how the data are arrange or where the data reside in the physical database.

User view or subschema: defines how a particular user sees the portion of the database that he or
she is authorized to access. So unlike internal and conceptual views, many distinct user views exist.
For example, a user in the personnel department may view the database as a collection of employee
records and is unaware of the supplier and inventory records seen by the users in the inventory control
department.

Second level of view is the data manipulation language or the DML. Data manipulation language
(DML) is the proprietary programming language, which a particular DBMS uses to retrieve, process and
stored data. This will be further explain by hazel sa kanyang report same with the third level of view
which is the query language.

Next we have, The database administrator or the DBA. The DBA is responsible for managing the
database resource. Having multiple users share a common database requires organization,
coordination, rules, and guidelines to protect the integrity of the database. Si DBA ang responsable
para sa pagpapanatili, pag-secure, at pagpapatakbo ng mga database and ineensure din na yung data
is correctly stored and retrive. Also, the DBA often work with the developers sa pagdedesign and pag
implement ng mga bagong features and mag solve sa mga troubleshoot issues.

Data dictionary: So this an another important function ni DBA, the creation and maintenance of the
data dictionary. The data dictionary describes every data element in the database. So si data dictionary
ineenable niya ang mga users or programmers to share a common view of the data resources and also
facilitates yung analysis ng user needs.

Last element of the database environment is the physical database. Si physical database siyaa
yung lowest level of the database. It consists of magnetic spots and magnetic disks. Physical database
represents, relational data objects kagaya ng tables, columns, primary and foreign keys ganyan and
also it represents their relations. Physical database design represents the materialization of a database
into an actual system.

Next topic, we have relational systems and others. What is a relational system? (read ppt for
definition). So in relational system, data is perceived by the users as tables and nothing but tables. Sa
relational database kasi eto yung type of database na nagiistore at nag proprovide ng access sa mga
data points na related to one another. Meron siyang 3 main operations. Una is select: nag crecreate
dito ng subset of data of records na nameet yung stated criteria. Pangalawa is Join: it Combines
relational data from different tables. And lastly Project: Creates a subset of a table using only specified
columns. Again this topic will be furtherly discuss by hazel sa topic na relational algebra.

Moving forward, next topic is the XML or the extensible markup language. A markup language is a
set of codes, or tags, that describes the text in a digital document. We have here an example of an
XML file. Nakikita natin yan minsan sa mga computer programmers kapag meron silang ginagawang
software or application or kung may need silang ayusin na part ng isang application so they use the
XML.

So what are the business applications of XML? XML helps businesses unify their information flows
since it introduces advanced data coding to Web sites. Information can be seamlessly exchanged
between Web sites, databases, and other back-end systems by developing a single set of XML tags for
all company data. So we have here business applications of XML. (read ppt)

Ngayon naman let’s compare the XML model and the relational model. So nakadepende parin kung
paano yung design ng database sa kung anong model yung gagamitin ng enterprise. So hindi porket
mas advantageous yung XML model eh yun na yung gagamitin natin, kailangan parin nating iassess
kung anong model ang mas magandang gamitin with the type of database you use than to be
dependent with the benefits only. So marami, maraming difference between XML model and the
relational model.
Una dyan, XML data is hierarchical; relational data is represented in a model of logical
relationships, So XML document nandyan yung mga information about relationship of data items to
each other in the form of hierarchy. While sa relational model naman, isa lang ang type of relationship
na pwedeng madefine, so it can be parent table and dependent table relationships only.

Next, XML data is self-describing; relational data is not, Sa XML kasi hindi lang data ang nilalaman
niya, it also contains tagging for the data which explains what the data is. Sa relational model naman,
yung nilalaman ng data is defined by its column definition.

And lastly, XML data has inherent ordering; relational data does not, let’s simply put it this way, sa
XML document, yung pagkakasunod ng data is yun na yung talagang order niya pero sa relational
model, hindi mo sure kung yung order is yun na talaga. Sa relational model kailangan mo pang ispecify
kung kaninong order iyon using columns and rows. Meaning XML model, there is no specification,
kapag relational model there is specification.

Last topic on my report, are the factors influencing data model choice. So kung kanina kinompare
natin yung dalawang models which is the XML and the relational model. Aalamin naman natin ano yung
pwedeng maka affect sa pagpili ng model na gagamitin natin in our database system.

First, When you need maximum flexibility, XML data is a better choice.

When you need maximum performance for data retrieval, relational data might be the better choice.
So kung more of issue ang focus natin, we need to use the relational model pero kung flexibility naman
ang paguusapan mas magandang gamitin ang XML model.

Next, When data is processed later as relational data, dito merong different scenarios, so kapag
yung processing of data depends on the data being stored in relational databases, mas maganda na
store nating yung mga data using relational model. Pero, if the processing of data requires storing of
data as XML document so mas maganda na store natin yung data using the XML model.

Next, When data components have meaning outside a hierarchy, bawat number kasi meron yang
description na kasama, so mas better na isama natin yung mga description in a relational table
because the relationship between the part numbers and the part descriptions is logically independent of
the purchase orders in which the part numbers are used.

Next, When data attributes apply to all data, or to only a small subset of the data, meron kasi
tayong data na matataas ang number of attributes so mas mahihirapan tayong ipresent yun using
relational model pero mas madali siyang ipresent kapag XML model.

When the ratio of data complexity to volume is high, so kapag mataas yung ratio of data complexity
mas magandang gamitin ang XML model.

Next, When referential integrity is required, kapag may referential integrity as much as possible, we
should use relational model. Kasi kapag XML model ang ginamit hindi niya kayang idefine as part of
referential constraints yung document na iyon.
And lastly, When the data needs to be updated often, it can be more efficient to use the XML model
because, whether it is large or small documents kayang kaya mastore yung data using the XML model.
And mas efficient to use si XML model data updates na ang focus.