Present and Future of DBMS

                            Present and Future of DBMS

                         ( Where database have been  ,where they are going )

Data is the power that runs a modern business.when cosumer of that power have different assumption ,a transformation is that  Transformation is required.very bad thing(including the loss of infrastructure investment)can happen if that transformation is not carefully planned.currently,there,are atleast thre major data management paradigms-ISAM,SQL/RELATIONAL,andXML-in use with XML poised the explode.each has different assumption regarding how data model the porganization’s view of the real world.when different models try to operate on the same source of power,they must recouncile these differences.

The process of reconciling these assumptions can result in data loss, performance degradation, system fragility, or feature availability. the ideal solution is for every consumer to enjoy native and natural access to the power source, without one model compromising another.

Database Management System-

 

Database management can be  thought having two principle ingredient-a data model and a system for implementing that model

 THE DATA MODEL IS  RESPONCIBLE FOR DESCRIBING THE PRINCIPLES BY WHICH the Data will represent the outside world. This model is implemented through a database management system (DBMS).

Database concept of concern-

First assumptions involve three relatively basic database concept-

    1-entities-the things that is being stored and is representative of something in the external world, such as customer, invoice, or inventory item.

   2-attributes- a descriptor of an entity

   3-relationship-a customer entity and three order entity are useless in a business process  unless you have some way of making their relationship persistence.

Now Journy From ISAM to XML:-

 Stages of database evolution-

 ISMA(indexed sequential access method)

It is developed by IDM  for mainfram computer it is a method for indexing data fast retrieval

Database technology has envolved through several stages, including ISMA,SQL?Relational,and XMLISAM-although ISAM has not been formaly standardized as a data model,in ISAM paradigm,entity are record.attributes are understood to be stored starting at a specific offset for specific length.the application is responsible for maintaining relationships,usualy performed in much the same ways as the realational model,where entities are collected in os files,and application is responsible to knowing which set of record is in which files.

An ISAM application act as if it is operating on the physical representation of  the record(which it is,most implementations)as a result much of the database management of  the ISAM paradigm is closely tied to both the operating system and the application

SQL/Relational

From a theoretical  standpoint, the SQL paradigm and relational model are not synonymous. In fact SQL can be used to build result set that does not meet the relational requirement. However,average  professional is not interested in purely theoretical DBMSs and when most people use a relational database,they are almost invariably use SQL to manipulate the data

XML:-(extensible markup language)

XML is not database paradigm.it is a portable persistence mechanism.however,in a distributed computing invironment ,XML fragment may be viewed as small ,disconnected database because the integration task required at the receiving end is equivalent to integrating data from two different database paradigms.each of these fragment(or minidatabase)is self-containing and confirm  to a set of rules.additional rules have been added by the introduction of XML schema,but these are not necessary to the exixtence of the XML fragment-it can under stood by an XML parser independently of additional rules.the additional rules are used primarily to easy the impedence mismatch that occurs when system of loosely structure data is incorporated into a system of more highly structure data.

Working with data across paradigm:-

 

It is not uncommon for business to have both ISAM and SQL application running side by side,the expected adoption of distributed computing requires that data can be used across all three paradigm as seamlessly as possible.much like the AC-DC conversion that takes place inside a transformer,the differences in assumption often result in a series of transformation that adapt data from one paradigm to another

What will post relational database look like?

There are any number of vision about the future of data storage. However, based on the history of database technology and practice, it would seem that a vision should assume at least the following trend-

1-database will continue to abstract their operations from application and OS dependencies

2-existing infrastructure investments will demand that data store in different paradigms can be accessed equally by all consumers

3-database models will be introduced with less frequency, but new ones will be introduced based on business needs.

4-there are a number of database concept that stays relatively untouched across models, even as the assumptions and constraints around those concept changes

 The desire evaluation of DBMSs therefore could take the form of a postrelatonal DBMS that decouples the storage mechanism from the access mechanism.

Conclusion-

The Organization has a great deal of investment in their infrastructure incorporation ISAM and relational models there are a number of competitive advantages that can be gained by distributed computing(such as Web Service)and the common language of distributed computing is XML.

The problem is that the XML model makes different assumptions about Data than the ISAM  and relational models.The result that that business are now tasked with adapting existing infrastructure to a new incompatible data model more quickly than never before.

There are several Possible  futures.as unlikely as it seems,distributed computing may turn out to be a fad.one particular mechanism of model adoption may improve to the point where it satisfactorily addresses the needs of most businesses. One of the models may evolve to accept assumption of the other model, making it reference model.

An ideal solution is a DBMS that can apply the content of any particular model to the underlying data,allowing existing infrastructure to perform at current levels while providing native and natural support for new model as needed.