Database Design

A database is considered self-describing because it contains metadata that describes its structure and organization. This metadata includes information about the tables, columns, data types, relationships, and other properties of the database. This allows users and applications to understand and interact with the database without needing external documentation.

"Plastic memory" refers to a phenomenon in which a material temporarily retains a deformation or shape after being subjected to stress, but eventually returns to its original shape once the stress is removed. This is often seen in certain types of plastics or materials that exhibit viscoelastic behavior.

The objectives of fact-finding include gathering accurate and reliable information, understanding the current situation or problem, identifying potential solutions, and making informed decisions based on evidence. It helps in uncovering the root cause of issues, determining the impact of different factors, and improving overall transparency in decision-making processes.

The foreign key is used as a reference in a table to the primary key of another table. For example: consider a table employee with id(primary key), name, address,department_id(foreign key) as its fields.Another table department with fields department_id(primary key) and dept_name.

So, department_id is primary key in department table and foreign key in employee table.

Join.

The three basic aspect of database securities are as follows:

1) User authentication while accessing data from database.

2) Data integrity should also me maintained.

3) Data schema should be properly defined.

Relational database state is a union of all the individual relation states, whenever the database is changed a new state arise. Relational state is also cartesian product of degree n on domain.

Union compatibility refers to the ability to combine two sets of data with the same structure and data types into a single dataset, usually by appending one set of data to another. Both sets must have the same number of columns, and those columns must have matching data types for union compatibility to be possible.

A primary key is always unique and not null. It is prefer to choose a field that is unique like roll number . But to choose Last name as a primary key is not a good option as two people can have same last name.

A Last name field is not a good one for a primary key. A primary key cannot have duplicate values. A last name field is highly likely to have duplicate values, so it should not be used as a primary key.

Relational database has many advantages over the flat file database:

1. Avoids data duplication.

2. Avoids inconsistent records.

3. Easier to change data.

4. Easier to change data format.

5. Data can be added and removed easily.

6. Easier to maintain security.

Relational databases offer structured data storage, data integrity through constraints like foreign keys, efficient querying using SQL, and support for complex data relationships through normalization.

Advantages:

1. Data integrity: Ensures consistency and accuracy of data.
2. Scalability: Able to handle large amounts of data and users.
3. Flexibility: Supports complex queries and relational structures.

Disadvantages:

1. Performance: Slower compared to NoSQL databases for some use cases.
2. Cost: Can be expensive to set up and maintain.
3. Schema rigidity: Requires predefined schema, making it less suitable for unstructured data.

A relational database is a database that stores data in the form of tables as well as defines relationship between those tables. A RDBMS helps in maintaining data integrity and consistency. Due to greater searching capabilities there is increased overhead.

see the link below http://www.freetutes.com/systemanalysis/sa8-comparison-relational-model-oo-model.html Different database models differ in their representation of relationships. In relational model, connections between two relations are represented by foreign key attribute in one relation that reference the primary key of another relation. Individual tuples having same values in foreign and primary key attribute are logically related. They are physically not connected. Relational model uses logical references. In object oriented model, relationships are represented by references via the object identifier (OID). This is in a way similar to foreign keys but internal system identifiers are used rather than user-defined attributes. The Object Oriented model supports complex object structures by using tuple, set, list, and other constructors. It supports the specification of methods and the inheritance mechanism that permits creation of new class definitions from existing ones. In relational model, each base relation is implemented as a separate file. If the does not specify any storage structure, most RDBMS will store the tuples as unordered records in the file. It allows the user to specify dynamically on each file a single primary or clustering index and any number of secondary indexes. It is the responsibility of user to chObject Orientedse the attributes on which the indexes are set up. Some RDBMSs give the user the option of mixing records from several base relations together. It is useful when related records from more than one relation are often accessed together. This clustering of records physically places a record from one relation followed by the related records from another relation. In this way the related records may be retrieved in most efficient way possible. Object Oriented systems provide persistent storage for complex-structured objects. They employ indexing techniques to locate disk pages that store the object. The objects are often stored as byte strings, and the object structure is reconstructed after copying the disk pages that contain the object into system buffers. Relational model has keys, entity integrity, and referential integrity. The constraints supported by Object Oriented systems vary from system to system. The inverse relationship mechanism supported by some Object Oriented systems provides some declarative constraints. There are languages such as SQL, QUEL, and QBE are available for relational systems. These are based on the relational calculus. In Object Oriented systems, the DML is typically incorporated into some programming language, such as C++. Hence, the structures of both stored persistent objects and programminglanguage transient objects are often compatible. Query languages have been developed for Object Oriented databases. Work on a standard Object Oriented model and language is progressing, but no complete detailed standard has emerged as yet.

A Relational Database is designed and maintained following some very well defined rules of logic and algebra. It often portrays a "one to many" relationship between two sets of data, and, less often, a "one to one" and "many to many" relation can be developed. An OO database uses less rigid design parameters, and can be adjusted design-wise to fit almost any kind of data environment. In fact, I'm not absolutely sure there is such a thing as an "object oriented" database, so much as there are database objects that are created and maintained with OO programming. I know that sounds self-referenceing, but that's OO for you... A relational database uses structure to locate and display data values, rather than programming logic. With a correctly designed RDB, finding and displaying data is very simple, compared to earlier network databases. Relational databases also permit the use of JOINS to merge and match sets of data ("relations"), to glean more information from your database that would normally be available.

Two important historical contributions in database development and design are the development of the relational model by E.F. Codd in the 1970s, which introduced the concept of relational databases and structured query language (SQL), and the creation of the first commercial database management system (DBMS) by IBM called IMS in the 1960s, which laid the foundation for modern database systems.

There is a software development certification with that name. There are also several other meanings for CSDA; check the Wikipedia article "CSDA" for additional meanings.

Database management software interrogates a database by sending queries written in a specific database query language (e.g., SQL) to retrieve, update, and manipulate data. The software processes these queries to access the database and perform the requested operations efficiently. It uses mechanisms like query optimization and indexing to improve performance and ensure data integrity.

Information in a database is collected through data entry processes where users input data manually, or through automated processes that extract data from other sources. This data is then organized and stored within the database tables according to a predefined structure to ensure consistency and accuracy of the information.

They would call it a record, a row or a tuple.

In the structure of a database, the part consisting of several uniquely named components called data fields. Several data records make up a data file, and several data files make up a database.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

Strictly speaking, you do not put information into a database, you put data into it, and you get information out of it. However, people tend to use the terms data and information interchangeably when talking about databases. Data is stored in the database, specifically in tables. So tables would be your answer.

To put information into a database, you typically need to use a database management system (DBMS) such as MySQL, Oracle, or MongoDB. You would write SQL queries to insert data into specific tables within the database by specifying the values you want to store in each column. This process allows you to organize and store data efficiently for future retrieval and analysis.

The six components are as follows:

1) Hardware: Physical aspects of the information system

2) Software: Programs that are used to control the information system (e.g. operating systems or computer programs)

3) Databases: Storage of data that is later used by programs to produce relevant and meaningful information

4) Procedures: Policies that govern the operations of the information

5) People: One of the most overlooked factors when determining the success or failure of the information system

6) Telecommunication: communication between computer to computer or computer to human