As i see it 009

Oracle:

* This is how Oracle Maestro looks when you start it for the first time. Select the Database |Create Database Profiles main menu item to create profiles for the existing databases.

* After you have created the required database profiles (Create Database Profile Wizard) they appear in the explorer tree on the left. Now you can establish connection to the database. If connection succeeds, the database node expands displaying the tree of its objects.


* New tables are created within Create Table Wizard. In order to run the wizard you should either

• select the Object | Create Database Object... main menu item;
• select the Table icon in the Create Database Object dialog

or
• select the Tables list or any object from that list in the explorer tree;
• select the Create New Table... item from the popup menu

or
• open and the Tables tab there;
• press the Insert key or select the Create New Table item from the popup menu (alternatively, you may use the corresponding link of the Navigation Bar).


FileMaker:

* You select from a palette of files, fields, and graphic tools to create a structure.

* The first step in designing a database is choosing what information you want to store in a database.

* The second step is to create fields in your file. This requires deciding what types of fields you want. For example, fields can store text, numbers, pictures, or other kinds of data.

* The third step is to create layouts. Layouts are computer screens that present information to you. Usually a database provides graphic tools that can enhance the appearance of the layout. For example, you can add boxes, lines, and fill patterns by using the tool palette.



Firebird:

* database are made in the Create Database Wizard.

* To run the Create Database Wizard, select the Database | Create New Database... main menu item or click the Create New Database button on the main toolbar.

* The first wizard step allows you to set a name of the new database.

* Database Editor allows you to browse all the database objects and its main properties. There is possible to create, edit and drop database sub-items.




SQLite:

* just click the "Create New Database" button from the main menu item

* this will lead you to the Create Database Wizard

* once you have accomplish filling up some informations in the Wizard window, you have now your database

* in making tables, you must first connect to a database.

* once you have connected, just right-click the database item in the explorer tree. Then, click "Create New Table".

As i see it 008

DB2 has a long history and is considered by many to have been the first database product to use SQL (also first developed by IBM).

The name DB2 was first given to the Database Management System or DBMS in 1983 when IBM released DB2 on its MVS mainframe platform. Prior to this, a similar product was named SQL/DS on the VM mainframe. The earlier System 38 platform also contained a relational DBMS. System Relational, or System R, was a research prototype developed in the 1970s. DB2 has its roots back to the beginning of the seventies when Dr. E.F. Codd, working for IBM, described the theory of relational databases and in June of 1970 published the model for data manipulation. To apply the model Codd needed a relational database language which he named Alpha. At the time IBM didn't believe in the potential of Codd's ideas, leaving the implementation to a group of programmers not under Codd's supervision, who violated several fundamentals of Codd's relational model; the result was Structured English QUEry Language or SEQUEL. When IBM released its first relational database product, they wanted to have a commercial-quality sublanguage as well, so it overhauled SEQUEL and renamed the basically new language SQL to differentiate it from SEQUEL. SQL, contrary to popular belief, does not stand for Structured Query Language as "it breaks the cardinal rule of structured languages by allowing branches to remote locations."(Allen G. Taylor, 2004) This leads the reader to speculate as to what the "true" meaning of SQL might be.

Historically, it is interesting to note that when Informix acquired Illustra and made their database engine an object-SQL DBMS by introducing their Universal Server, both Oracle and IBM followed suit by changing their database engines to be capable of object-relational extensions. Moreover, in 2001, IBM bought Informix and in the following years incorporated Informix technology into the DB2 product suite. Today, DB2 can technically be considered to be an object-SQL DBMS.

For some years DB2, as a full-function DBMS, was exclusively available on IBM mainframes. Later IBM brought DB2 to other platforms, including OS/2, UNIX and Windows servers, then Linux (including Linux on zSeries) and PDAs. This process was mainly undertaken through the 1990s. The inspiration for the mainframe version of DB2's architecture came in part from IBM DL/1 and IBM IMS, both initially hierarchical and then later network (or CODASYL) databases. DB2 is also embedded in the i5/OS operating system for IBM System i (iSeries, formerly the AS/400), and versions are available for z/VSE and z/VM.

An earlier version of the code that would become DB2 LUW (Linux, Unix, Windows) was part of an Extended Edition component of OS/2 called Database Manager. IBM extended the functionality of Database Manager a number of times, including the addition of distributed database functionality that allowed shared access to a database in a remote location on a LAN. Eventually IBM declared that insurmountable complexity existed in the Database Manager code, and took the difficult decision to completely rewrite the software in their Toronto Lab. The new version of Database Manager, called DB2 like its mainframe parent, ran on the OS/2 and RS/6000 platforms, was called DB2/2 and DB2/6000 respectively. Other versions of DB2, with different code bases, followed the same '/' naming convention and became DB2/400 (for the AS/400), DB2/VSE (for the DOS/VSE environment) and DB2/VM (for the VM operating system). IBM lawyers stopped this handy naming convention from being used and decided that all products needed to be called "product FOR platform" (for example, DB2 for OS/390). The next iteration of the mainframe and the server-based products were named DB2 Universal Database (or DB2 UDB), with the introduction of widespread confusion over which version (mainframe or server) of the DBMS was being referred to. At this point, the mainframe version of DB2 and the server version of DB2 were coded in entirely different languages (PL/S for the mainframe and C++ for the server), but shared very similar functionality and used a common architecture for SQL optimization: the Starburst Optimizer.

Over the years DB2 has both exploited and driven numerous hardware enhancements, particularly on IBM System z with such features as Parallel Sysplex data sharing. In fact, DB2 UDB Version 8 for z/OS now requires a 64-bit system and cannot run on earlier processors, and DB2 for z/OS maintains certain unique software differences in order to serve its sophisticated customers. Although the ultimate expression of software-hardware co-evolution is the IBM mainframe, to some extent that phenomenon occurs on other platforms as well, as IBM's software engineers collaborate with their hardware counterparts.

In the mid-1990s, IBM released a clustered DB2 implementation called DB2 Parallel Edition, which initially ran on AIX. This edition allowed scalability by providing a shared nothing architecture, in which a single large database is partitioned across multiple DB2 servers that communicate over a high-speed interconnect. This DB2 edition was eventually ported to all Linux, UNIX, and Windows (LUW) platforms and was renamed to DB2 Extended Enterprise Edition (EEE). IBM now refers to this product as the Database Partitioning Feature (DPF) and sells it as an add-on to their flagship DB2 Enterprise product.

In mid 2006, IBM announced "Viper," which is the codename for DB2 9 on both distributed platforms and z/OS. DB2 9 for z/OS was announced in early 2007. IBM claims that the new DB2 will be the first relational database to store XML "natively". Other enhancements include OLTP-related improvements for distributed platforms, business intelligence/data warehousing-related improvements for z/OS, more self-tuning and self-managing features, additional 64-bit exploitation (especially for virtual storage on z/OS), stored procedure performance enhancements for z/OS, and continued convergence of the SQL vocabularies between z/OS and distributed platforms.

DB2 9 on distributed platforms began shipping worldwide on July 28, 2006, with pricing starting at $4,874 per processor or $165 per user (minimum of 5 users) for DB2 9 Express, including one year of support.[1] DB2 for z/OS pricing starts at about $4,450 per month, including support.

As i see it 007

Correlate and differentiate the ff:

* folder
* file
* record
* datafield

Differentiate:

A folder/database-contains records, and in which each record is specified in a single line.

Stores information such as text and images.

A tuple is analogous to a record in non relational databases. The term originated as an abstraction of the sequence: single, double, triple, quadruple, quintuple, ... n-tuple. Tuple is used in abstract mathematics to denote a multidimensional coordinate system.

A data field is a place where you can store data. Commonly used to refer to a column in a database or a field in a data entry form or web form. A data field is a place where you can store data. Commonly used to refer to a column in a database or a field in a data entry form or web form. The field may contain data to be entered as well as data to be displayed.

Correlation:
-Information in the database is generally stored in several different files. Each file consists of series of records. Each records consists of several fields, with each field containing an individual data item.

-fields, records, files and objects optimized to deal with very large amounts of data stored on a permanent structure.

As i see it 006

Differentiate all basic data models and alternative data models:

1).Hierarchical Models-data is organized into a tree-like structure. The structure allows repeating information using parent/child relationships: each parent can have many children but each child only has one parent. All attributes of a specific record are listed under an entity type. In a database, an entity type is the equivalent of a table; each individual record is represented as a row and an attribute as a column. Entity types are related to each other using 1: N mapping, also known as one to many relationships. The most recognized example of hierarchical model database is an IMS designed by IBM.
2.)Network Model-is a data modelsconceived as a flexible way of representing objects and their relationships. Its original inventor was charles,Becham and it was developed into a standard specification published in 1969 by the CODASYL Consortium. Where the hiererchical model structures data as a tree of records, with each record having one parent record and many children, the network model allows each record to have multiple parent and child records, forming a lattice structure.

The chief argument in favour of the network model, in comparison to the hierarchic model, was that it allowed a more natural modeling of relationships between entities. Although the model was widely implemented and used, it failed to become dominant for two main reasons. Firstly, IBM chose to stick to the hierarchical model with semi-network extensions in their established products such asnd DL/I. Secondly, it was eventually displaced by relational model the which offered a higher-level, more declarative interface. Until the early 1980s the performance benefits of the low-level navigational interfaces offered by hierarchical and network databases were persuasive for many large-scale applications, but as hardware became faster, the extra productivity and flexibility of the relational model led to the gradual obsolescence of the network model in corporate enterprise usage.

3.)Relational Models-is the easiest models to use and understand. Instead of creating files,records,owners,members,parents,or children, you create a table containing rows and columns.You design each table to eliminate redundancy and link them toghether using foreign keys.

4.)Entity-relationship model-is an abstract conceptual representation of structured data. Entity-relationship modeling is a relational schema database modeling method, used in software engineering to produce a type of conceptual data model (or semantic data model) of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created using this process are called entity-relationship diagrams, or ER diagrams or ERDs for short. Originally proposed in 1976 by Dr. Pin-Shan (Peter) Chen (陳品山), many variants of the process have subsequently been devised.

5.)Object-relational Model-similar to a relational database, but with an object-oriented database model: objects, classes and inheritance are directly supported in database schemas and in the query language. In addition, it supports extension of the data model with custom data-types and methods.

One aim for this type of system is to bridge the gap between conceptual data modeling techniques such as Entity-relationship diagram (ERD) and object-relational mapping (ORM), which often use classes and inheritance, and relational databases, which do not directly support them.

As i see it 005

♦Identify at least 10 BDMS software with their corresponding developer.

10 BDMS Software - Developers

1.) Jet Database Engine- Microsoft
2.) SQL Server - Microsoft
3.) Visual FoxPro - Microsoft
4.) IBM DB2 Express-C - IBM
5.) Virtuoso Universal Server - OpenLink Software
6.) FileMaker - Nashoba Systems of Concord
7.) Firebird - InterBase/Firebird product line
8.) SQL Server Express - Microsoft
9.) Access - Microsoft
10.) Dataphor - Alphora,

Visual FoxPro

Visual FoxPro is a data-centric object-oriented and procedural programming language produced by Microsoft. It is derived from FoxPro (originally known as FoxBASE) which was developed by Fox Software beginning in 1984. Fox Technologies merged with Microsoft in 1992, after which the software acquired further features and the prefix "Visual". The last version of FoxPro (2.6) worked under Mac OS, DOS, Windows, and Unix: Visual FoxPro 3.0, the first "Visual" version, dropped the platform support to only Mac and Windows, and later versions were Windows-only. The current version of Visual FoxPro is COM-based and Microsoft has stated that they do not intend to create a Microsoft .NET version.

FoxPro originated as a member of the class of languages commonly referred to as "xBase" languages, which have syntax based on the dBase programming language. Other members of the xBase language family include Clipper and Recital. (A history of the early years of xBase can be found in the dBASE entry.)

Visual FoxPro, commonly abbreviated as VFP, is tightly integrated with its own relational database engine, which extends FoxPro's xBase capabilities to support SQL query and data manipulation. Unlike most database management systems, Visual FoxPro is a full-featured, dynamic programming language that does not require the use of an additional general-purpose programming environment. It can be used to write not just traditional "fat client" applications, but also middleware and web applications.

As i see it 004

CORRELATE:
DATA WITH DATABASE
MANAGEMENT WITH SYSTEM

DATA with DATABASE:

Data is stored information in the computer created by a user.It is stored as files in the computer.
Database is a structured collection of datas or records.The relation between data and database is that when you store a data in the computer it will be called as database,because it is already structured as files.


MANAGEMENT with SYSTEM:

Management in simple terms is the act of getting together to accomplish desired goals.
System is a set of interacting or interdependent entities, real or abstract, forming an integrated whole.
The relation between management and system is when there is no management there is no system.In computers there is relationship between hardware and software,manages all devices,so thats what we called system.No management no system.

As i see it 003

Discuss And Interrelate the following:
♦Data
♦Data Type
♦Data Structure
♦DBMS

Data is a collection of some information or descriptions in to a certain thing. in Data Type, it is an attribute of a datum(a single data) which tells the computer (and the programmer) something about the kind of datum it is. This involves setting constraints on the datum, such as what values it can take and what operations may be performed upon it. In Data Structure, it is being stored in the computer so that it can be used efficiently. Often a carefully chosen data structure will allow the most efficient algorithm to be used. A well-designed data structure allows a variety of critical operations to be performed, using as few resources, both execution time and memory space, as possible. In DBMS, A Data Base Management System is a complex set of software programs that controls the organization, storage, management, and retrieval of data in a database.

Data Structure are implemented by a programming language as data types and the references and operations they provide. DBMS are categorized according to their data structures or types, some time DBMS is also known as Data base Manager. It is a set of prewritten programs that are used to store, update and retrieve a Database. A DBMS includes:
1. A modeling language to define the schema of each database hosted in the DBMS, according to the DBMS data model.
2.* The four most common types of organizations are the hierarchical, network, relational and object models. Inverted lists and other methods are also used. A given database management system may provide one or more of the four models. The optimal structure depends on the natural organization of the application's data, and on the application's requirements (which include transaction rate (speed), reliability, maintainability, scalability, and cost).

3.* The dominant model in use today is the ad hoc one embedded in SQL, despite the objections of purists who believe this model is a corruption of the relational model, since it violates several of its fundamental principles for the sake of practicality and performance. Many DBMSs also support the Open Database Connectivity API that supports a standard way for programmers to access the DBMS.

4. Data structures (fields, records, files and objects) optimized to deal with very large amounts of data stored on a permanent data storage device (which implies relatively slow access compared to volatile main memory).

5. A database query language and report writer to allow users to interactively interrogate the database, analyze its data and update it according to the users privileges on data.

6.It also controls the security of the database.

7.*Data security prevents unauthorized users from viewing or updating the database. Using passwords, users are allowed access to the entire database or subsets of it called subschemas. For example, an employee database can contain all the data about an individual employee, but one group of users may be authorized to view only payroll data, while others are allowed access to only work history and medical data.

8.*If the DBMS provides a way to interactively enter and update the database, as well as interrogate it, this capability allows for managing personal databases. However, it may not leave an audit trail of actions or provide the kinds of controls necessary in a multi-user organization. These controls are only available when a set of application programs are customized for each data entry and updating function.

9. A transaction mechanism, that ideally would guarantee the ACID properties, in order to ensure data integrity, despite concurrent user accesses (concurrency control), and faults (fault tolerance).

10.It also maintains the integrity of the data in the database.

11.The DBMS can maintain the integrity of the database by not allowing more than one user to update the same record at the same time. The DBMS can help prevent duplicate records via unique index constraints; for example, no two customers with the same customer numbers (key fields) can be entered into the database. See ACID properties for more information (Redundancy avoidance).

The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data.

When a DBMS is used, information systems can be changed much more easily as the organization's information requirements change. New categories of data can be added to the database without disruption to the existing system.

Organizations may use one kind of DBMS for daily transaction processing and then move the detail onto another computer that uses another DBMS better suited for random inquiries and analysis. Overall systems design decisions are performed by data administrators and systems analysts. Detailed database design is performed by database administrators.

Database servers are specially designed computers that hold the actual databases and run only the DBMS and related software. Database servers are usually multiprocessor computers, with RAID disk arrays used for stable storage. Connected to one or more servers via a high-speed channel, hardware database accelerators are also used in large volume transaction processing environments.

DBMSs are found at the heart of most database applications. Sometimes DBMSs are built around a private multitasking kernel with built-in networking support although nowadays these functions are left to the operating system.