Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
325 views

Date's Twelve Rules For Distributed Database Systems

Here are the steps to find the names and salaries of employees who are assigned to projects for over 12 weeks in MySQL/SQL: 1. Join the EMP, ASG, and PAY tables on employee number (eno) and title. 2. Filter the results where the assignment duration (dur) is greater than or equal to 12. 3. Select the employee name (ename) and salary (sal) from the joined tables. So the SQL query would be: SELECT a.ename, c.sal FROM EMP a JOIN ASG b ON a.eno = b.eno JOIN PAY c ON a.title = c.title WHERE b.dur >= 12;

Uploaded by

ozila jazz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
325 views

Date's Twelve Rules For Distributed Database Systems

Here are the steps to find the names and salaries of employees who are assigned to projects for over 12 weeks in MySQL/SQL: 1. Join the EMP, ASG, and PAY tables on employee number (eno) and title. 2. Filter the results where the assignment duration (dur) is greater than or equal to 12. 3. Select the employee name (ename) and salary (sal) from the joined tables. So the SQL query would be: SELECT a.ename, c.sal FROM EMP a JOIN ASG b ON a.eno = b.eno JOIN PAY c ON a.title = c.title WHERE b.dur >= 12;

Uploaded by

ozila jazz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

The University of Faisalabad

Submitted by:
Daud Khalid (Bscs-fa18-015)
BSCS-6th

Subject:
Distributed Database Management System

Submitted to:
Miss Anum Nawaz

Assignment # 1

Department of Computational Science


Amin campus
Question # 1:
Date's Twelve Rules for Distributed Database Systems:
1) Local Autonomy: he sites in a distributed system should be
autonomous. In this context, autonomy means that:
i. Local data is locally owned and managed.
ii. Local operations remain purely local.
iii. All operations at a given site are controlled by that site.
2) No reliance on a central site: There should be no one site without
which the system cannot operate. This implies that there should be no
central servers for services such as transaction management, deadlock
detection, query optimization, and management of the global system
catalog.
3) Continuous Operation: Ideally, there should never be a need for a
planned system shutdown, for operations such as: n adding or
removing a site from the system; n the dynamic creation and deletion
of fragments at one or more sites.
4) Location Independence: Location independence is equivalent to
location transparency. The user should be able to access the database
from any site. Furthermore, the user should be able to access all data
as if it were stored at the user’s site, no matter where it is physically
stored.
5) Fragmentation Independence: The user should be able to access the
data, no matter how it is fragmented.
6) Replication Independence: The user should be unaware that data
has been replicated. Thus, the user should not be able to access a
particular copy of a data item directly, nor should the user have to
specifically update all copies of a data item.
7) Distributed query processing: The system should be capable of
processing queries that reference data at more than one site.
8) Distributed transaction processing: The system should support the
transaction as the unit of recovery. The system should ensure that
both global and local transactions conform to the ACID rules for
transactions, namely: atomicity, consistency, isolation, and durability.
9) Hardware independence: It should be possible to run the DDBMS
on a variety of hardware platforms.
10) Operating system independence: As a corollary to the previous
rule, it should be possible to run the DDBMS on a variety of
operating systems.
11) Network independence: Again, it should be possible to run the
DDBMS on a variety of disparate communication networks.
12) Database independence: It should be possible to have a DDBMS
made up of different local DBMSs, perhaps supporting different
underlying data models. In other words, the system should support
heterogeneity. The last four rules are ideals. As the rules are so
general, and as there is a lack of standards in computer and network
architectures, we can expect only partial compliance from vendors in
the foreseeable future.
Question # 2:

Find the names and salaries of employees who are assigned to projects for over
12 weeks.
Practical in MySQL/SQL?

Query:
SELECT a.ename, c.sal
FROM EMP a, ASG b, PAY c
WHERE a.eno = b.eno
AND a.title = c.title
AND b.dur >= 12;

You might also like