Scribd
Upload
40 views4 pages

Python Report

The document discusses distributed databases. It defines a distributed database as one that is spread across multiple computers or sites rather than being confined to a single system. Distributed databases are useful when data needs to be accessed by users around the world. The data is managed to appear as a single set to users. The document discusses horizontal and vertical fragmentation for splitting tables across sites. It also provides details on the SDLC model used, work division for the project, and key phases of design, implementation, testing, operation, and maintenance of distributed databases.

Uploaded by

rise empire
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
40 views4 pages

Python Report

The document discusses distributed databases. It defines a distributed database as one that is spread across multiple computers or sites rather than being confined to a single system. Distributed databases are useful when data needs to be accessed by users around the world. The data is managed to appear as a single set to users. The document discusses horizontal and vertical fragmentation for splitting tables across sites. It also provides details on the SDLC model used, work division for the project, and key phases of design, implementation, testing, operation, and maintenance of distributed databases.

Uploaded by

rise empire
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Introduction:

A distributed data base is fundamentally an information base that isn't restricted to one
framework, it is spread over various locales, i.e., on numerous PCs or over an organization of
PCs. An appropriated data base system is situated on different sited that don't share actual parts.
This perhaps required when a specific data set should be gotten to by different clients around the
world. It should be overseen with the end goal that for the clients it would appear that one single
data set.
Horizontal fragmentation – Splitting by columns – The connection is divided into gatherings of
tuples so each tuple is appointed to in any event one section.
Vertical fragmentation – Splitting by segments – The composition of the connection is isolated
into more modest diagrams. Each piece should contain a typical applicant key in order to
guarantee lossless join.

Work Division:
The following chart show the complete work division for the project we have completed.

SDLC Model:
The SDLC Model is used is V-Model and other models can also be used in this Project.
Initial:
 Observe company condition
 Operating Zone
 Company structure
 Define Faults and constraints
 Define Goals
 Define scope/domain and boundaries

Design:
 Most Crucial DBLC stage
 Makes sure final product meets the need
 Focus on data requirements
 Subphases
 Create logical design
1. DBMS workstation selection
2. Create conceptual design
3. Create blueprints of the designs

Implementation:

 Creating special storage-related constructs to house end-user tables.


 Data uploaded into tables.
 Other Problems.
1. Performance
2. Security
3. Backup and recovery
4. Integrity
5. Company standards
6. Concurrency controls

Testing:

 Database is tested and fine-tuned for performance, integrity, concurrent access, and security
constraints
 Done in parallel with application programming
 Actions taken if tests fail
1. Fine-tuning based on reference manuals
2. Modification of physical design
3. Modification of logical design
4. Upgrade or change DBMS software or hardware

Operation:

 Database considered operational


 Starts process of system evaluation
 Unforeseen problems may surface
 Demand for change is constant

Maintenance & Evaluation:


 
 Caution maintenance
 Error maintenance
 Adaptation maintenance
 Assignment of access permissions
 Creation of database access statistics to monitor performance
 Periodic security audits based on system-generated statistics
 Periodic system usage-summaries
Conclusion:
Through this paper, we need to pull in readers towards the profitable side of disseminated data
sets. We likewise referenced the product engineering being utilized for the circulated information
base. We additionally depicted Fragmentation, replication and recuperation viewpoint
additionally to make readers totally mindful about the theme being portrayed here. Other than
having a productive side of DDBs, it likewise pulls in scientists for tracking down the new
extension in it.

References:
1. https://www.tutorialspoint.com/distributed_dbms/distributed_dbms_database_environments.
htm
2. https://www.cse.ust.hk/ct/fyp/reports/content/project_planning.html
3. http://www.pkirs.utep.edu/cis4365/Tutorials/Database%20Design/General
%20Design/Tutorial%207.00100/tutorial%207.00100.htm
4. http://www.pkirs.utep.edu/cis4365/Tutorials/Database%20Design/General
%20Design/Tutorial%207.00100/tutorial%207.00100.htm

You might also like