Scribd
Upload
62 views

What Is Database Architecture

Database architecture focuses on designing software programs that store and organize information for businesses. It determines how data is structured and accessed. Common database architectures include 1-tier, 2-tier, and 3-tier structures. 1-tier keeps all elements like interface and data in one place. 2-tier uses a client-server model with direct communication between client and server. 3-tier separates components into three tiers based on user complexity and data use. Normalization is the process of optimizing database structures by removing redundancies and anomalies. First normal form ensures each attribute contains a single value. Second normal form removes partial dependencies, while third normal form removes transitive dependencies.

Uploaded by

gaurav
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
62 views

What Is Database Architecture

Database architecture focuses on designing software programs that store and organize information for businesses. It determines how data is structured and accessed. Common database architectures include 1-tier, 2-tier, and 3-tier structures. 1-tier keeps all elements like interface and data in one place. 2-tier uses a client-server model with direct communication between client and server. 3-tier separates components into three tiers based on user complexity and data use. Normalization is the process of optimizing database structures by removing redundancies and anomalies. First normal form ensures each attribute contains a single value. Second normal form removes partial dependencies, while third normal form removes transitive dependencies.

Uploaded by

gaurav
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

What Is Database Architecture?

Database architecture uses programming languages to design a particular type of


software for businesses or organizations.Database architecture focuses on the design,
development, implementation and maintenance of computer programs that store and
organize information for businesses, agencies and institutions. A database architect
develops and implements software to meet the needs of users.

The design of a DBMS depends on its architecture. It can be centralized or decentralized


or hierarchical. The architecture of a DBMS can be seen as either single tier or multi-tier.
The tiers are classified as follows :

1. 1-tier architecture

2. 2-tier architecture

3. 3-tier architecture

4. n-tier architecture

1-tier architecture:
One-tier architecture involves putting all of the required components for a software
application or technology on a single server or platform.

1-tier architecture
Basically, a one-tier architecture keeps all of the elements of an application, including the
interface, Middleware and back-end data, in one place. Developers see these types of
systems as the simplest and most direct way.

2-tier architecture:
The two-tier is based on Client Server architecture. The two-tier architecture is like client
server application. The direct communication takes place between client and server.
There is no intermediate between client and server.

2-tier architecture

3-tier architecture:
A 3-tier architecture separates its tiers from each other based on the complexity of the
users and how they use the data present in the database. It is the most widely used
architecture to design a DBMS.
3-tier architecture
1st Normal Form Example
How do we bring an unnormalized table into first normal form? Consider the following
example:

This table is not in first normal form because the [Color] column can contain multiple
values. For example, the first row includes values “red” and “green.”

To bring this table to first normal form, we split the table into two tables and now we
have the resulting tables:
Now first normal form is satisfied, as the columns on each table all hold just one value.

Second Normal Form:

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

In a table, if attribute B is functionally dependent on A, but is not functionally dependent


on a proper subset of A, then B is considered fully functional dependent on A. Hence, in a
2NF table, all non-key attributes cannot be dependent on a subset of the primary key.
Note that if the primary key is not a composite key, all non-key attributes are always fully
functional dependent on the primary key. A table that is in 1st normal form and contains
only a single key as the primary key is automatically in 2nd normal form.

2nd Normal Form Example


Consider the following example:

This table has a composite primary key [Customer ID, Store ID]. The non-key attribute is
[Purchase Location]. In this case, [Purchase Location] only depends on [Store ID], which
is only part of the primary key. Therefore, this table does not satisfy second normal form.

To bring this table to second normal form, we break the table into two tables, and now
we have the following:
What we have done is to remove the partial functional dependency that we initially had.
Now, in the table [TABLE_STORE], the column [Purchase Location] is fully dependent
on the primary key of that table, which is [Store ID].

Third Normal Form:

A relation is in third normal form if it is in 2NF and no non key attribute is transitively
dependent on the primary key.

A bank uses the following relation:

Vendor(ID, Name, Account_No, Bank_Code_No, Bank)

The attribute ID is the identification key. All attributes are single valued (1NF). The table
is also in 2NF.

The following dependencies exist:

1. Name, Account_No, Bank_Code_No are functionally dependent on ID (ID → Name,


Account_No, Bank_Code_No)

2. Bank is functionally dependent on Bank_Code_No (Bank_Code_No → Bank)


The table in this example is in 1NF and in 2NF. But there is a transitive dependency
between Bank_Code_No and Bank, because Bank_Code_No is not the primary key of
this relation. To get to the third normal form (3NF), we have to put the bank name in a
separate table together with the clearing number to identify it.

You might also like