Essay Properties: 1. 2. 3. 4. 5. 6. The essay is a wake up call and provocative (BUT not offensive and not insulting), thought-provoking, challenging, simulating, inspiring, interesting, and motivating. Introduce the topic to general audience but has enough for making it interesting to specialized group in the field Pick on debatable, controversial, and arguable issues Propose new ideas for research and practices Encourage reader to think (special) & to respond or reply. Mostly, there are no references (a few (one or two) is fine.) List for Ideas for essays: Software Stability in Any Database Modeling Transition to a New Database Technology Problem Partition in Database Design Problem Understanding in Database Design Pattern Languages for any Database Type Role of database in Dynamic Analysis Model-Based Architectures for Database Models Business Issues: The impact of database on: Business Rules Business Models Business Patterns Business Standards Business Transformation Business Strategy Models Business Optimization Business Process Design Enduring Business Processes Business Security and Privacy Service-Oriented Architectures Business Standards for Extended Enterprise Information Integration Framelets role in database design Patterns: Utilizing patterns in Database Design Stable Analysis Patterns Stable Design Patterns Stable Architectural Patterns Systems of Patterns Pattern Languages Stable Testing Patterns Timeless Architectures Quality Factors in Database Design: Reusability Extensibility Maintainability Testability Adaptability Scalability Safety Reliability Resilience Understandability Complexity Portability Usability Efficiency Learnability Etc. Knowledge Maps for Constraints Databases Spatiotemporal Databases Transaction Management Spatial Database Temporal Database Relational Database Object Database Distributed Database Data Animation Data Visualization Data Mining Data Farming Data Warehousing Generate one of the following patterns ATOMICITY: a transaction should be done or undone completely. In the event of an error or failure, all data manipulations should be undone, and all data should rollback to its previous state. CONSISTENCY: a transaction should transform a system from one consistent state to another consistent state. ISOLATION: each transaction should happen independently of other transactions occurring at the same time. DURABILITY: Completed transactions should remain stable/permanent, even during system failure. Normalization Normalization is the process of organizing data to minimize redundancy and remove ambiguity. Normalization involves separating a database into tables and defining relationships between the tables. There are three main stages of normalization called normal forms. Each one of those stages increases the level of normalization. The 3 main normal forms are as follows: First Normal Form (1NF): Each field in a table must contain different information. Second Normal Form (2NF): All attributes that are not dependent upon the primary key in a database table must be eliminated. Third Normal Form (3NF): No duplicate information is permitted. So, for example, if two tables both require a common field, this common field information should be separated into a different table. There are 2 more normalization forms, fourth normal form (4NF) and fifth normal form (5NF), but they are rarely used. Normalization makes databases more efficient and easier to maintain. Query Queries are the main way to make a request for information from a database. Queries consist of questions presented to the database in a predefined format, in most cases SQL (Structured Query Language) format. Transaction Transaction is a group of SQL database commands regarded and executed as a single atomic entity. Trigger Triggers are special type of stored procedures executed automatically when certain events take place. There are different types of triggers – for update, for insert and for delete. Each trigger is associated with a single database table. Catalog In computing, a catalog is a directory of information about data sets, files, or a database. A catalog usually describes where a data set, file or database entity is located and may also include other information, such as the type of device on which each data set or file is stored.