learn-oracle
free Oracle DBA tutorial Oracle Jobs
Ask A Question
SQL Statement Tuning
Backup and Recovery Concepts
Oracle 11g New Features
Oracle E Suite & Others
Oracle Data Guard
Oracle DBA FAQ





Oracle DBA - Data Modeling


Page :  1  2  3



Data Modeling: Finding the Perfect Fit

The purpose of data modeling is to develop an accurate model, or graphical representation, of the client's information needs and business processes. The data model acts as a framework for the development of the new or enhanced application. There are almost as many methods of data modeling as there are application development methodologies. CNS uses the Oracle CASE*Method for its data modeling.

Data modelling layers: do you wanna get logical or physical

In the bad old days we used to progress from "current physical" to "current logical" models. We then used to transform the "current logical" to the "new logical" and about then the deadline cut in and we scurried about hacking the code for the new system which is about as "new physical" as you can get. No wonder the agile people noticed that it made more sense to devote your time and intelligence to the "new physical", which wasn't going to be thrown away soon after you finished.

Database Modeling Using Visio

A previous article covered some of the features of Visio, "The Microsoft Office Business and Technical Diagramming Program." One of Visio's key features is its ability to reverse engineer a database, and in this article, we will take a look at doing exactly that using the sample schemas Oracle provides. Comparing the results of Visio's reverse engineering and the schema diagrams illustrated in the Oracle Database Sample Schemas documentation, and seeing how well they match should give you some confidence in Visio's features. The version of Visio used in these examples is the Professional 2003 edition.

Database normalization

In relational database theory, normalization is the process of restructuring the logical data model of a database to eliminate redundancy, organize data efficiently, reduce repeating data and to reduce the potential for anomalies during data operations. Data normalization also may improve data consistency and simplify future extension of the logical data model. The formal classifications used for describing a relational database's level of normalization are called normal forms.



Database Normalization Basics

In this article, we'll introduce the concept of normalization and take a brief look at the most common normal forms. Future articles will provide in-depth explorations of the normalization process.

Design of Oracle tables

For the purpose of these guidelines a table is a two-dimensional array of data (made up of rows and columns) that the data user sees (whether, in Oracle parlance, it is a physical table or a view).

General Database Design FAQ

There are two ways of constructing a software design; one way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult."

Normalization

Normalization is a design technique that is widely used as a guide in designing relational databases. Normalization is essentially a two step process that puts data into tabular form by removing repeating groups and then removes duplicated data from the relational tables. Normalization theory is based on the concepts of normal forms. A relational table is said to be a particular normal form if it satisfied a certain set of constraints. There are currently five normal forms that have been defined. In this section, we will cover the first three normal forms that were defined by E. F. Codd.

Normalization and tracking systems

We have all been taught to normalize our relational databases to at least the third normal form. This eliminates data redundancy and decreases the size of the database. This has a lot of benefits, too many for me to list. However, there is a problem that occurs when a designer applies normalization principles on a work tracking system. Even the most experienced database designers overlook this problem, and it will cause problems in the work/performance reports.

Oracle Data Modeling, Breaking & Fixing First Normal Form (1NF)

It has been my observation that a lot of us lack the basic skills required to model the simplest of database objects. This article will explore some of the common mistakes and fixes to the breaking of 1NF.

Page :  1  2  3

More Tutorials on Oracle dba ...


Liked it ? Want to share it ? Social Bookmarking

Add to: Mr. Wong Add to: BoniTrust Add to: Newsider Add to: Digg Add to: Del.icio.us Add to: Reddit Add to: Jumptags Add to: StumbleUpon Add to: Slashdot Add to: Netscape Add to: Furl Add to: Yahoo Add to: Spurl Add to: Google Add to: Blinklist Add to: Technorati Add to: Newsvine Information




Want to share or request Oracle Tutorial articles to become a Oracle DBA. Direct your requests to webmaster@oracleonline.info






   Forum
Oracle Forum   
Google

Oracle DBA - Step 1
Oracle DBA - Step 2
Oracle DBA - Step 3
Oracle DBA - Step 4
Oracle DBA - Step 5
Oracle DBA - Step 6
Oracle DBA - Step 7
Oracle DBA - Step 8
Oracle DBA - Step 9
Oracle DBA - Step 10

SQL Statement Tuning
Backup and Recovery Concepts
Oracle 11g New Features
Oracle E Suite & Others
Oracle Data Guard
Oracle DBA FAQ