Standard-Relational and Object-Relational Databases
Software development has experienced evolution over the past few decades given the increasing demands for better information systems in today's society, especially in the modern business environment. The evolution of software development during this period has also been influenced by the tremendous changes in the ways with which computers are used and programmed. The changes in software development have contributed to the emergence of different categories of databases, which are basically defined as repositories for assorted but interrelated pieces of data or information. Through the evolution of software development, database management systems have been transformed. The most common classifications of databases emerging from the transformation of database management systems include standard-relational and object-relational databases.
Standard-relational databases are those that support interactive data structures and utilize data manipulation language that is akin to...
Since they utilize powerful data manipulation language, standard-relational databases are utilized for management of huge amounts of data. These databases are also suitable for retrieval of data through they provide very minimal support for manipulation of data (Robie & Bartels, n.d.). On the contrary, object-relational databases are relatively similar to standard-relational databases, but utilize an object-oriented database model. Based on this model, object-relational databases directly support classes, objects, and inheritance using database schemas and query languages. Object-relational databases, which are commonly known as object-relational database management systems, provide balance between standard-relational and object-oriented database management systems.
As evident in these definitions, there are similarities and differences between standard-relational and object-relational databases. One of the similarities between these two databases is that they both support data model extensions though tailor-made data types and techniques. Secondly, these databases are suitable for management of huge amounts of data and data retrieval because of the data languages they utilize. Third, the two databases are similar on the premise that they are based on a relational model in which data is arranged in at least two tables containing a unique identifier for each row. Through this model, standard-relational and object-relational databases contain interrelated data.
Despite these similarities, there are some huge differences including the fact that object-relational databases include an object-oriented database model unlike standard-relational databases. Given the use of an object-oriented database model, object-relational databases provide a balance between the standard-relational databases and object-oriented databases. Secondly, standard-relational databases are based on two-dimensional tables where every item appears as a row while…
This is one of the greatest limitations of this technology. A second major disadvantage of RDBMS-based systems is their lack of support for image- and spatial-based databases that include Computer-Aided Design (CAD) drawings, 3D rendering and model-based data. Their table-based structure is inefficient in defining the attributes of these data types and lacks the necessary data tagging and data types to manage imaging and CAD-based design files and data
Relational Databases in e-Commerce Of the many uses of relational databases throughout enterprise software their use for supporting e-commerce initiatives and programs provides a foundation for assessing their performance at diverse data and taxonomy management, and scalability of transactions as well. The scalability, security and speed of relational databases when used for e-commerce tasks push them to the limits of performance and customization as well. An example of this is the
They in short link and map ideas that already exist, creating real time answers to questions as they are applied to new and archived knowledge or action plans. According to IDC reports, most data warehouses will be stored in a columnar fashion and not in rows, reporting and data collection problems will be solved with databases that have no formal schema at all, horizontal scalability through clustering will be achieved
" "STUDENT INFORMATION TABLE" ( "STUDENT ID" CHARACTER (4) NOT NULL, NAME CHARACTER (25) NOT NULL, "STREET NUMBER" CHARACTER (10) NOT NULL, "STREET NAME" CHARACTER (25) NOT NULL, CITY CHARACTER (25) NOT NULL, STATE CHARACTER (10) NOT NULL, EMAIL CHARACTER (25) NOT NULL, "PHONE NUMBER" CHARACTER (15) NOT NULL ); CONNECT RESET; SQL FOR Book_Information CONNECT TO LIBRARY; CREATE TABLE "USER"; CREATE TABLE BookInformation ( "BookISBN" CHARACTER (10) NOT NULL; "AUTHOR" CHARACTER (25) NOT NULL; "TITLE" CHARACTER (50) NOT NULL; "PRICE" CHARACTER (10) NOT NULL; CONNECT RESET; SQL STATEMENT FOR
Database Administrator for Department Store Scenario The department store has expanded in the local region by opening five more bookstores, and the bookstore has launched a series of marketing campaign to increase sales and attract new customers. The objective of this technical report is to develop a plan to create and maintain an enterprise-wide database system that will assist the bookstore to hold the inventory and sales data. The database design will
Microsoft supports distributed component objects via distributed COM (DCOM). DCOM use remote procedure calls to organize data between processes and computers so that components appear to have the same word size, bit orientation, and address space. DCOM is a direct competitor to CORBA, discussed next. V. Common Object Request Broker Architecture (CORBA) CORBA is OMG's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks (CORBA Basics). Using