A

SSIGNMENT-4
Q ues1: What are the different SQL Standards and Standards for interoperability and
integration?

S olution:

 S QL Standards:

Oracle strives to comply with industry-accepted standards and participates actively in SQL
standards committees. Industry-accepted committees are the American National Standards
Institute (ANSI) and the International Organization for Standardization (ISO), which is affiliated
with the International Electro technical Commission (IEC). Both ANSI and the ISO/IEC have
accepted SQL as the standard language for relational databases. When a new SQL standard is
simultaneously published by these organizations, the names of the standards conform to
conventions used by the organization, but the standards are technically identical.

The latest SQL standard was adopted in July 2003 and is often called SQL: 2003. One part of the
SQL standard, Part 14, SQL/XML (ISO/IEC 9075-14) was revised in 2006 and is often
referenced as "SQL/XML: 2006". The formal names of this standard, with the exception of
SQL/XML, are:

 ANSI/ISO/IEC 9075:2003, "Database Language SQL", Parts 1 ("SQL/Framework"), 2

("SQL/Foundation"), 3 ("SQL/CLI"), 4 ("SQL/PSM"), 9 ("SQL/MED"), 10
("SQL/OLB"), 11("SQL/Schemata"), and 13 ("SQL/JRT")
 ISO/IEC 9075:2003, "Database Language SQL", Parts 1 ("SQL/Framework"), 2
("SQL/Foundation"), 3 ("SQL/CLI"), 4 ("SQL/PSM"), 9 ("SQL/MED"), 10
("SQL/OLB"), 11("SQL/Schemata"), and 13 ("SQL/JRT")

T he formal names of the revised part 14 are:

 ANSI/ISO/IEC 9075-14:2006, "Database Language SQL", Part 14 ("SQL/XML")

 ISO/IEC 9075-14:2006, "Database Language SQL", Part 14 ("SQL/XML")
O ther Standards are:

S QL Standard-SQL/XML Functionality:

Integration of SQL and XML, sql to XML data types, publishing SQL data with XML, mapping
SQL data and metadata to XML; and SQL and X-Query: integration of the xquery data model;
XML constructor functions, querying XML values.

I BM's SQL 1999 Presentation:

This SQL 1999 standards presentation was created by number of very well respected database
researchers from IBM who are on the ANSI and ISO database standards committees. This file
was created during the spring of 1999 and is thus slightly out of synch with the actual SQL 1999
standard. If an updated SQL 1999 presentation becomes available it will be posted. You will
notice that I have "borrowed" liberally from IBM's slides for the White marsh SQL 1999
presentations.

O racle's SQL: 1999 Presentation

This additional SQL 1999 standards presentation was created by Jim Melton who is the Editor of
the ANSI and ISO database standards committee base documents. This file was created during
the summer of 1999 and is thus more recent, but still slightly out of synch with the actual SQL
1999 standard. Again, if an updated SQL 1999 presentation becomes available it will be posted.
You will ALSO notice that I have "borrowed" liberally from IBM's slides for the White marsh
SQL1999.

D AMA 2000 SQL1999 Talk:

From 1986 through 1999, ANSI SQL standards have been based on two-dimensional tables. This
made SQL's data model relational, in the main. SQL1999, the new ANSI database languages
standard, has dramatically broken from the relational model and has specified complex, nested
data structures, its own programming language, Spatial and Full Text processing facilities, and
even Codasyl sets.

The purpose of this talk is to review these "new" facilities and to identify the impact they will
have on database design, data administration, database administration, and database application
development. Finally the talk presents the results of an informal survey among the key vendors
as to their SQL1999 implementation directions.
S QL: 1999, The Presentation (736K):

This 70+ page presentation presents the materials from the Great News paper and includes
overheads that show examples of some of the syntax and data structures possible under SQL
1999. You can get the SQL 1999 standard for a nominal fee from INCITS (International
Committee for IT Standards).

S QL1999 Bill of Materials (1.41M):

The SQL 1999 Bill of Materials database application provides both a database of the SQL 1999
standard features. The database unfolds like a set of nested directories and each item includes
some level of explanatory text. This software is NOT contained within an installer. You must
UnZip the files and place them into a drive and directory of your choice. Once there, you merely
execute the program, SQL_BOM.exe. Software items here are 32 bit. They have been tested on
Windows 95/98/00 and NT.

R elational Data Model "RIP" overhead (70K):

Presenting SQL 1999. This overhead will be great to use when focusing your screen. Do NOT
use this overhead with groups that think that Codd and _od rhyme.

G eneology of SQL1999Standard:

 S tandards for Interoperability and Integration:

Integration is a term with different meanings in different contexts – from being a very precise
term in mathematics, as the art of calculating integrals, to a more ambiguous term in social
sciences and everyday speech, as in cultural, ethnic, or religious integration. Similarly, in our
field of HIS, meanings of integration will vary according to ‘who you are’, your role in the
organization, your relation to the health sector, and the perspectives on the HIS. While managers
and health services providers would think that integration of information and routines are needed
to perform certain tasks; ICT staff, software developers and more technically-oriented personnel
would think that co-ordination of the software applications and protocols for communication are
needed to achieve that. During an electronic forum debate on integration, in the RHINO network
meeting in Mexico, 2009, it turned out that, while some saw integration strictly as a technical
term related to collating several software applications into ‘one system,’ regarded as a negative
and an old fashioned approach; others used integration to describe approaches to get health
programmers to collaborate and unify their data collection forms and routines. Those who
understood the term integration as referring to a technical approach to make ‘one big system’,
were against the notion of integration understood in this way. They would rather go for the
concept of interoperability, as they saw it more useful to make different systems to interoperate
rather than to collapse them into one big system. In our view, however, integration, even at the
level of software applications, cannot be reduced to an aim of constructing one big system. The
definition of integration in the organizational context, takes the user’s needs of the HIS, the
purpose of the systems, and the wider organizational perspectives as points of departure, and
relate those two goals of better efficiency, effectiveness and co-ordination in organizations and
enterprises. In such a perspective, interoperability is one of the means to achieve such ends –
integration. Interoperability is, contrary to integration, a term which may be given a more formal
definition. In our context, interoperability refers to the ability of a system to use and share
information or functionality, of another system by adhering to common standards. Without
agreed standards shared by at least two systems, processes or other actors which are aiming at
interoperability, interoperability is not possible. In the last chapter, we described the example of
the SDMX-HD standard for exchange of data. Two ‘levels’ of standards are needed in order to
exchange data; a shared format or protocol, for example the SDMX-HD, and then, of course, one
needs to agree on what data including their definition and meaning should be transferred. Later
in this chapter, we discuss the distinction between syntactic and semantic standards, and
elaborate on the challenges of developing data standards. But for now, we use the example of
SDMX-HD to describe the essence of interoperability.

An example from Sierra Leone Building Interoperability In late 2009, WHO had initiated a
process to develop a data exchange standard for health metadata and statistics, building on an
existing standard for financial transactions. This new protocol, SDMX-HD, was still not
implemented by any application, far less in any real use-case setting by early 2010. Nevertheless,
HMN, MoH in Sierra Leone and HISP, decided to initiate a pilot system that could both track
patients on Antiretroviral Therapy (ART) and share this data with the data warehouse running on
DHIS2, as stipulated in the original strategic plan for the country. OpenMRS, a medical record
application, was set up in the main hospital in Freetown, the capital. Weeks before this took
place in February 2010, major advancements were made to SDMX-HD, spurred by the fact that
it was about to be implemented in two ‘live’ applications. The main idea was that OpenMRS has
the functionalities needed for doctors and nurses to track patients over time, while the aggregate
data from this system is used for general health management at hospital, district, and national
levels. This two-level use applies to other domains and applications also, such as logistics
management, human resource management, lab systems, health finances, and so on. With
SDMX-HD set to go live in Sierra Leone at the given date, developers behind DHIS2 and
OpenMRS not only pushed development forward by implementing this standard in the respective
applications, they also contributed the necessary use-case to solve outstanding issues. The
development of SDMX-HD made the HIS architecture of various applications for different
business domains, a reality; anyone able to share data on this protocol could now be ‘plugged in’
in a country HIS.

While HMN and HISP were collaborating in Sierra Leone; CapacityPlus, a partner of HISP and
HMN, specializing in strengthening health workforce information systems, was partnering with
the West Africa Health Organization (WAHO), to pilot open source human resource
management software called iHRIS, in Ghana. Learning about the ‘Sierra Leone architecture’,
WAHO took the initiative to include also the iHRIS suite of applications for human resource
management in this architecture, which provided further impetus to the iHRIS implementation of
SDMX-HD. These initiatives, together with the fact that many countries in the West African
region were in the process of introducing the DHIS2 and/or the iHRIS, led to the organisation of
a workshop on training in both these applications in Accra, Ghana, September 2010. This
workshop was jointly supported by WAHO, HMN, WHO, CapacityPlus and HISP. The WHO
organized a ‘Connectathon’ meeting for the SDMX-HD in parallel with the workshop. At the
end of the workshop, the SDMX-HD standard was officially launched and implemented in the
DHIS2, the iHRIS, OpenMRS, and the WHO Indicator Measurement Registry (IMR) integrated
framework. This initiative was further consolidated in November 2010, where HIS staff from all
the 15 WAHO member states was present. There, it was decided that HMN, WAHO, HISP, and
CapacityPlus should collaborate to develop a centre of excellence at WAHO, for supporting
member countries in adopting the interoperable solutions which had grown out of Sierra Leone.

I nteroperability:

It is the ability to exchange data between two or more systems. In Figure , we see exchange of
data:

 Between DHIS2 and OpenMRS.

 Between DHIS2 and iHRIS.

This is where; we have interoperability between, in this case, two systems. There is no
interoperability between OpenMRS and IHRIS.

I ntegration:

Here, can be understood as the process of joining distinct systems in such a way, that they appear
as being a whole in a particular perspective. In this case, we see that patient data from OpenMRS
and human resource data from iHRIS are ‘joined’ and integrated in the DHIS2 ‘data warehouse’.
OpenMRS and iHIRS are integrated, but there is no interoperability between them. DHIS2 is
interoperable with both OpenMRS and iHRIS. Figure emphasizes a technically biased
perspective on interoperability, since it is seen strictly as an interaction between two software
applications. Such a technical perspective is quite usual and may seem the reason why the
concept of interoperability has been mostly used and promoted by those with more technical
and/or clinical medical backgrounds, who view the term as being mostly related to a medical
records system. However, if we ‘unpack’ the SDMX-HD interoperability arrow in Figure, we see
that it includes both the SDMX-HD standard for data exchange and the data which is to be
exchanged. We may regard these two components and their internal relationship as being similar
to the messenger and the message; the container and the content; and between syntax and
semantics.

Q ues2: Write notes on Oracle, IBM DB2 Universal Database in detail with examples.

S olution: Oracle Database:

Oracle database (Oracle DB) is a relational database management system (RDBMS) from the
Oracle Corporation. Originally developed in 1977 by Lawrence Ellison and other developers,
Oracle DB is one of the most trusted and widely-used relational database engines.

The system is built around a relational database framework in which data objects may be directly
accessed by users (or an application front end) through structured query language (SQL). Oracle
is fully scalable relational database architecture and is often used by global enterprises, which
manage and process data across wide and local area networks. The Oracle database has its own
network component to allow communications across networks.

Oracle DB is also known as Oracle RDBMS and, sometimes, just Oracle.

Oracle DB rivals Microsoft’s SQL Server in the enterprise database market. There are other
database offerings, but most of these command a tiny market share compared to Oracle DB and
SQL Server. Fortunately, the structures of Oracle DB and SQL Server are quite similar, which is
a benefit when learning database administration.

Oracle DB runs on most major platforms, including Windows, UNIX, Linux and Mac OS.
Different software versions are available, based on requirements and budget. Oracle DB editions
are hierarchically broken down as follows:

 E nterprise Edition: Offers all features, including superior performance and security, and
is the most robust
 S tandard Edition: Contains base functionality for users that do not require Enterprise
Edition’s robust package
 Express Edition (XE): The lightweight, free and limited Windows and Linux edition
racle Lite: For mobile devices
 O

A key feature of Oracle is that its architecture is split between the logical and the physical. This
structure means that for large-scale distributed computing, also known as grid computing, the
data location is irrelevant and transparent to the user, allowing for a more modular physical
structure that can be added to and altered without affecting the activity of the database, its data or
users. The sharing of resources in this way allows for very flexible data networks whose capacity
can be adjusted up or down to suit demand, without degradation of service. It also allows for a
robust system to be devised as there is no single point at which a failure can bring down the
database, as the networked schema of the storage resources means that any failure would be local
only.
I BM DB2 Universal Database:

IBM Db2 is a family of hybrid data management products offering a complete suite of AI-
empowered capabilities designed to help you manage both structured and unstructured data on
premises as well as in private and public cloud environments. Db2 is built on an intelligent
common SQL engine designed for scalability and flexibility.
Originally released by IBM in 1983 as the company’s first commercially available relational
database, Db2 continues to deliver innovation as an industry-leading platform for efficient hybrid
data management. It drives high-impact data insights, seamless business continuity and real
business transformation. The Db2 data management revolution continues today with its
availability on IBM Cloud Pak for Data, a modern data and AI platform built on a cloud-native
architecture using Red Hat Open Shift. This platform delivers predictive and proactive actionable
insights into customer behavior to help businesses grow market share, reduce costs and deliver
successful AI initiatives.

DB2 UDB, V8.2 builds on its market-proven industrial strength and on demand capabilities with
the following key enhancements:

 Reduces deployment and management costs

o Design Advisor
o Automated statistics collection and object maintenance
o Self-tuning backup and restore
 Increases programmer productivity
o Microsoft.NET integration
o Java enhancements, including thin client and integrated help
 Provides a robust infrastructure
o High Availability Disaster Recovery (HADR)
o Automated client reroute
o Linux scalability
o Security
 Extends the value of information
o New queue-based replication architecture
o Geodetic Extender
 IBM DB2 Universal Database® (UDB) V8.2 offers industry-leading database
performance, as highlighted in recent TPC-C and TPC-H benchmarks, while helping
customers simplify and automate many of the tasks associated with deploying databases.
As a result, organizations can free up skilled DBA resources to focus on next-generation
enterprise applications, such as Business Intelligence, Content Management, or
Information Integration, and further lower their total cost of ownership (TCO).
 This DB2® UDB release delivers over 200 new features; some are highlighted below:
 Design Advisor, an industry-leading innovative technology that assists DBAs in making
optimal and comprehensive database design decisions. It is a self-configuring autonomic
tool that greatly simplifies the database design process by using workload, database, and
hardware information to recommend optimal design of database objects.
 Automated statistics profiling represents the first deployment from IBM's learning
optimizer (LEO) research and development project. LEO is the next generation of IBM's
query optimizer technology, in which the database automates, simplifies, and accelerates
queries without human intervention.
 Autonomic Object Maintenance feature automatically performs policy-based
administration and maintenance functions, such as table reorganization, statistics
collection, and database backup.
 To improve programmer productivity and provide choice of programming
environments, DB2 UDB provides deep integration with, or plug-ins for, both
Java™/Eclipse and Microsoft™ .NET IDEs, such as IBM WebSphere ® Studio and
Microsoft Visual Studio .NET.
 High Availability Disaster Recovery (HADR) and client reroute features enable 24x7
information availability and resilience required by on demand enterprises.
 DB2's Linux™ leadership is extended by supporting the distributions based on the new
2.6 kernel. Exploitation of new I/O and memory management features found in the latest
Linux distributions is provided. 64-bit Linux versions of DB2 servers are provided for
Linux on Intel™ EM64T, Linux on POWER™ (IBM pSeries® and iSeries™),
and Linux on IBM zSeries® hardware architectures.
 DB2 UDB Geodetic Extender supports treatment of the Earth like a globe rather than a
flat map. Thus, making it easier to develop applications for business intelligence and e-
government that require geographical location analysis.
Q ues3: Discuss different XML specifications in ADBMS?

S olution:

XML Database is used to store huge amount of information in the XML format. As the use of
XML is increasing in every field, it is required to have a secured place to store the XML
documents. The data stored in the database can be queried using XQuery, serialized, and
exported into a desired format.

X ML Specifications:

X ML Database Types
There are two major types of XML databases −

 XML- enabled
 Native XML (NXD)

X ML - Enabled Database
XML enabled database is nothing but the extension provided for the conversion of XML
document. This is a relational database, where data is stored in tables consisting of rows and
columns. The tables contain set of records, which in turn consist of fields.
N ative XML Database
Native XML database is based on the container rather than table format. It can store large
amount of XML document and data. Native XML database is queried by the XPath-
expressions.
Native XML database has an advantage over the XML-enabled database. It is highly capable to
store, query and maintain the XML document than XML-enabled database.

E xample:-
Following example demonstrates XML database −
<?xml version ="1.0"?>
<contact-info>
<contact1>
 <name>TanmayPatil</name>
<company>TutorialsPoint</company>
<phone>(011) 123-4567</phone>
</contact1>

<contact2>
<name>ManishaPatil</name>
<company>TutorialsPoint</company>
<phone>(011) 789-4567</phone>
</contact2>
</contact-info>

Here, a table of contacts is created that holds the records of contacts (contact1 and contact2),
which in turn consists of three entities − name, company and phone.