For the first time I am faced with Northwind , many different definitions in his blog, "is a database containing the tables to be used as a test, easily erasable" or the more concise 'is the Word of the DB hello ".. ok ..
is a Northwind database (this is a set of data and objects, contains tables, queries, forms, reports, pages, macros and modules) and a project (an Access file is linked to a Microsoft SQL Server to create client applications / server) Access which contains data relating to sales of
a fictitious company called Northwind Traders, which imports and exports specialty foods around the world. From the view of objects in the Northwind database can be drawn inspiration to create custom databases for their own needs.
: To create a new DB operations were not too difficult, however, given the elementary exercise: building Access database with data about enrollment, registrations and registrations at the Sapienza University.
File -> new; DB -> empty; appointed by my name and then saved, and creates the table in Design view, create table with the wizard and creates the table with direct entry of data. I so drawn to Access a double entry table. Which is good to encode each element may
CS = code 1, 2 Stat code, code 3 Wis.
year 2207-2008 = code 1, code 2 2008-2009, 2009-2010 code 3.
.. the goal is to eliminate redundancy in order to analyze / edit data in a consistent way, in this case allows an analysis for both years and for faculty. With Northwind, you can create relationships between different data from the various tables, but it should be noted that the data "split" into different tables must be joined by a code (the relationship between Primary Key and Foreign Key. The relationship is between 1 to n the primary key and all the foreign keys). The normalization
Col Normalization is the process of organizing data in the database. You create tables, you define the relationships between them based on rules designed to protect data and make the database flexible by eliminating redundancy and inconsistent dependencies.
The presence of redundant data results in a waste of disk space and maintenance problems of Db. If you must change the data in different tables, the change must always be in the same way. It is easier to make a change on the address / phone of a student if the students are all stored in the same table and with a certain mode.
It 'important to keep in mind what an "inconsistent dependency" because it certainly is intuitive for a user to look in the Students table to address a specific student, but can not make sense to look in that table information identifying the qualification the parents of that student. Such information is related to the student but will be placed in another table linked to the first by a code that the joints. But if you decide not to make a real normalization, please make sure that the application is able to prevent possible problems arising, such as redundant data and inconsistent dependencies.
The denormalization
From the speech made so far suggests that the quality of a Db is directly proportional to the distribution of data in the reports. The question, however, is more complex because the splitter data in reports following the task of reconstruction of the original information.
There is talk of denormalization, the operation that leads to merge attributes belonging to different relations in a single report to better performance on our investigation on the basis of data.
A case of denormalization occurs with the creation of attributes that contain data from other reports. This can be accomplished through the query : Question a database to obtain the data contained in one or more databases. Usually, a query is passed to the DBMS in SQL (Structured Query Language). And 'so the command being sent to the DBMS and requires a denormalized table!
If we consider our database with faculty and students, to know which option is written each time a student should have the power associated with tuples from the report particular student.
(A tuple is a generic element of a relationship with attributes in a relational database. It is the basic entity that must be stored in the database. Es: zoo = 'wolf', 'elephant', 'penguin'. The variable refers to a zoo tuple of elements (values)). An alternative solution would be to store the number directly in the report "students", increasing it each new year or less confirmed when your registration to which ones may. In this way access to such information would be immediate. But you know, everything has a cost! The denormalization increases the complexity of software that uses the database, because it will be directly responsible for updating the data, and therefore increase the risk of inconsistency of data stored.
is a Northwind database (this is a set of data and objects, contains tables, queries, forms, reports, pages, macros and modules) and a project (an Access file is linked to a Microsoft SQL Server to create client applications / server) Access which contains data relating to sales of
a fictitious company called Northwind Traders, which imports and exports specialty foods around the world. From the view of objects in the Northwind database can be drawn inspiration to create custom databases for their own needs.
: To create a new DB operations were not too difficult, however, given the elementary exercise: building Access database with data about enrollment, registrations and registrations at the Sapienza University.
File -> new; DB -> empty; appointed by my name and then saved, and creates the table in Design view, create table with the wizard and creates the table with direct entry of data. I so drawn to Access a double entry table. Which is good to encode each element may
CS = code 1, 2 Stat code, code 3 Wis.
year 2207-2008 = code 1, code 2 2008-2009, 2009-2010 code 3.
.. the goal is to eliminate redundancy in order to analyze / edit data in a consistent way, in this case allows an analysis for both years and for faculty. With Northwind, you can create relationships between different data from the various tables, but it should be noted that the data "split" into different tables must be joined by a code (the relationship between Primary Key and Foreign Key. The relationship is between 1 to n the primary key and all the foreign keys). The normalization
Col Normalization is the process of organizing data in the database. You create tables, you define the relationships between them based on rules designed to protect data and make the database flexible by eliminating redundancy and inconsistent dependencies.
The presence of redundant data results in a waste of disk space and maintenance problems of Db. If you must change the data in different tables, the change must always be in the same way. It is easier to make a change on the address / phone of a student if the students are all stored in the same table and with a certain mode.
It 'important to keep in mind what an "inconsistent dependency" because it certainly is intuitive for a user to look in the Students table to address a specific student, but can not make sense to look in that table information identifying the qualification the parents of that student. Such information is related to the student but will be placed in another table linked to the first by a code that the joints. But if you decide not to make a real normalization, please make sure that the application is able to prevent possible problems arising, such as redundant data and inconsistent dependencies.
The denormalization
From the speech made so far suggests that the quality of a Db is directly proportional to the distribution of data in the reports. The question, however, is more complex because the splitter data in reports following the task of reconstruction of the original information.
There is talk of denormalization, the operation that leads to merge attributes belonging to different relations in a single report to better performance on our investigation on the basis of data.
A case of denormalization occurs with the creation of attributes that contain data from other reports. This can be accomplished through the query : Question a database to obtain the data contained in one or more databases. Usually, a query is passed to the DBMS in SQL (Structured Query Language). And 'so the command being sent to the DBMS and requires a denormalized table!
If we consider our database with faculty and students, to know which option is written each time a student should have the power associated with tuples from the report particular student.
(A tuple is a generic element of a relationship with attributes in a relational database. It is the basic entity that must be stored in the database. Es: zoo = 'wolf', 'elephant', 'penguin'. The variable refers to a zoo tuple of elements (values)). An alternative solution would be to store the number directly in the report "students", increasing it each new year or less confirmed when your registration to which ones may. In this way access to such information would be immediate. But you know, everything has a cost! The denormalization increases the complexity of software that uses the database, because it will be directly responsible for updating the data, and therefore increase the risk of inconsistency of data stored.