Database Schema - Revision history

User at 23:14, 12 April 2023

2023-04-12T23:14:22Z

User at 23:09, 12 April 2023

2023-04-12T23:09:30Z

User at 18:10, 4 January 2023

2023-01-04T18:10:26Z

User at 07:00, 16 October 2022

2022-10-16T07:00:34Z

User at 23:09, 15 October 2022

2022-10-15T23:09:53Z

User: Created page with "'''Content Coming Soon'''"

2018-12-20T01:34:24Z

Created page with "'''Content Coming Soon'''"

New page

'''Content Coming Soon'''

@@ Line 12: / Line 12: @@
 == See Also ==
-[[Entity Relationship Model]]
+[[Entity Relationship Diagram (ERD)]]
 __NOTOC__

@@ Line 1: / Line 1: @@
-== What is Database Schema? ==
+A '''Database Schema''' is a structure that describes the organization of data in a database. It specifies the tables, fields, relationships, and other elements that make up the database and defines how the data is stored and accessed.
-A '''database schema''' is a structure that describes the organization of data in a database. It specifies the tables, fields, relationships, and other elements that make up the database, and defines how the data is stored and accessed.
+A database schema can be represented visually using a diagram called an Entity Relationship Diagram (ERD). An ERD shows the different entities in the database and their relationships. For example, an ERD for a database of employees might include entities for employees, departments, and projects and show the relationships between these entities (e.g., an employee works in a department and is assigned to one or more projects).
 There are several types of database schemas, including:
 *Physical schema: This is the actual organization of data in the database, including the data types, sizes, and other characteristics of the fields.
-*Logical schema: This is the organization of data as it is perceived by the user. It describes the relationships and meanings of the data, but not the physical details of how it is stored.
+*Logical schema: This is the organization of data as it is perceived by the user. It describes the relationships and meanings of the data but not the physical details of how it is stored.
-*View schema: This is a virtual representation of the data, created by selecting and combining data from multiple tables or views.
+*View schema: This is a virtual representation of the data created by selecting and combining data from multiple tables or views.
 == See Also ==
+[[Entity Relationship Model]]
+__NOTOC__

← Older revision		Revision as of 18:10, 4 January 2023
Line 1:		Line 1:
−	'''~~Content Coming Soon~~'''	+	== What is Database Schema? ==
		+
		+	A '''database schema''' is a structure that describes the organization of data in a database. It specifies the tables, fields, relationships, and other elements that make up the database, and defines how the data is stored and accessed.
		+
		+	A database schema can be represented visually using a diagram called an Entity Relationship Diagram (ERD). An ERD shows the different entities in the database and the relationships between them. For example, an ERD for a database of employees might include entities for employees, departments, and projects, and show the relationships between these entities (e.g., an employee works in a department and is assigned to one or more projects).
		+
		+	There are several types of database schemas, including:
		+	*Physical schema: This is the actual organization of data in the database, including the data types, sizes, and other characteristics of the fields.
		+	*Logical schema: This is the organization of data as it is perceived by the user. It describes the relationships and meanings of the data, but not the physical details of how it is stored.
		+	*View schema: This is a virtual representation of the data, created by selecting and combining data from multiple tables or views.
		+
		+	The database schema is an important part of the database design process, as it determines how the data is stored and accessed. A well-designed schema can make it easier to use and maintain the database, while a poorly designed schema can lead to problems such as data redundancy, inconsistencies, and poor performance.

@@ Line 4: / Line 4: @@
 == See Also ==
-*[[Business_Strategy|Business Strategy]]
-*[[IT_Strategy_(Information_Technology_Strategy)|IT Strategy]]
-*[[E-Strategy|e-Strategy]]
-*[[IT_Governance|IT Governance]]
-*[[Enterprise_Architecture|Enterprise Architecture]]
+== References ==
-*[[IT_Sourcing_(Information_Technology_Sourcing)|IT Sourcing]]
+<references />

← Older revision		Revision as of 23:09, 15 October 2022
Line 1:		Line 1:
	'''Content Coming Soon'''		'''Content Coming Soon'''
		+
		+
		+
		+	== See Also ==
		+	*[[Business_Strategy\|Business Strategy]]
		+	*[[IT_Strategy_(Information_Technology_Strategy)\|IT Strategy]]
		+	*[[E-Strategy\|e-Strategy]]
		+	*[[IT_Governance\|IT Governance]]
		+	*[[Enterprise_Architecture\|Enterprise Architecture]]
		+	*[[IT_Sourcing_(Information_Technology_Sourcing)\|IT Sourcing]]
		+	*[[IT Operations_(Information_Technology_Operations)\|IT Operations]]
		+	*[[Chief_Information_Officer_(CIO)\|CIO]]