For those outlines that do not satisfy the normal shapes the normalization is carried out, that it concurs to obtain the intentional quality.
Moreover, the planning methodologies that have been adopted up to now, allow of usual to obtain outlines that they satisfy the forms of normal schools.
Therefore this passage is more one verification that not true and just a passage of normalization.
The redundancies and the anomalies have been studied cross them so-called dependencies work them, that is a type tie works them between the attributes of one relation. These dependencies work allow them the presence of tuple between equal they on the attributes. A relation r on an outline R(X) is given and two sottoinsiemi of not empty attributes Y and Z of X, we will say that it exists on r a dependency works them between Y and Z if, for every brace of tuple T1 and t2 of r having the same values on the Y attributes, it turns out that T1 and t2 has same values also on the attributes of Z.
The taken normal shape as reference in this job is the Normal Shape of Boyce and Codd: that is a relation r is in this shape if, for every dependency X work them not banal? Y defined on it, X contains one K key of r, that is X are superkey for r, that is allow to identify all separately the tuple.
The first relation that is analyzed is:
WAREHOUSE (ID_Magazzino, Center, Position GPS, Owner)
A dependency would exist works them between Center and Owner, because it is possible that the same owner can have more warehouses in the same center, and if the same owner had as single tie that one of having warehouses in the same center (as an example industrial zone). In order to avoid this dependency it must be attention to the meant one that "Center" is given to the term.
The second one is:
BUBBLE (ID_Bolla, ID_Magazzino_Cedente, ID_Prodotto, Des_prod, Quantitative, ID_Trasp, Data_Richiesta, Data_Consegna)
Sussisterebbe a dependency works them between ID_Prodotto and ID_Trasp, if the conveyors were used to always carry the same type of product. It could happen, but given the type of products it transports to you in the Districts, this is one hypothesis difficult, even if not impossible.
From how much it has been looked at, the previous planning has given already turns out hopes to you to you, and the cases of dependencies work them not banal are somewhat remote.
THE PHYSICAL PLANNING
Once the two finished are made previous, it is passed to the physical planning, that is they choose the software specific, the architecture hardware on which implementing the job and the physical characteristics that allow to manage the DB.
This phase is but unavoidable from the real case, that is is closely necessary to know the number of customers, the volume of the accesses, gives to you more uses you; without to count that the various architectures have various costs of investment and maintenance.
The only part that can be carried a.termine in this phase, a.tito it esplicativo, is the choice of the software and the creation of the database true and just through the same one.
Referring to the case of the Plan of Virtual Warehouse, the chosen applicativo is Microsoft SQL Server 2000 (Trial Version), easy reperibile on the given market its elevated spread.
The first phase has been that one of the creation of the tables from the relations previously created.
As an example, the table "Warehouse that it demands", had relational shape
WAREHOUSE (ID_Magazzino, Center, Position GPS, Owner)
Every single table will come defined in automatic way, leaving from a code SQL standard that the same SQL Server generates.
The tables to they time will have of the columns whose tito them they correspond to the attributes that are assign to you in the relations.
These attributes will have one they particular, characteristic shape of the type with which they will have to be represents to you.
As an example it is chosen to identify the warehouse with a type code decimates them with precision, that is the maximum number of figures decimates used them in the represent of that value, maximum ten.
Moreover value NULL is not allowed, also because ID_Magazzino is primary key of the relation.
This passage for every relation is carried out.
To the end of this phase the relations between tables are introduced.
As an example, the warehouse petitioner emits one demanded of the lacking material, and this action is rappresentabile through one relation, that is "Demanded Material".
The relation is possible for the existing tie between ID_Mag_Rich and ID_Magazzino.
The complete picture is what it follows:
Once placed the relations, the job base is made.
Its possible to carry out other passages for affinare and personalizing the use of the database.
As an example they can (or in some cases the CHECK ties must) be introduced, that they allow to guarantee integrity of give to you.
A characteristic operation, a lot used in this database is that one on the minimal and maximum length of the present values in the occurrences.
As an example, it is important to have a length value univoco in order to identify the codes of the products:
LEN (ID_Prodotto) = 6.
Other values respect in all the tables to you are (to character of the all indicative):
| Attribute | Length |
| Produced Code | 6 |
| Code Warehouse | 4 |
| Code Conveyor | 6 |
| Demanded Code | 10 |
| Code Bubble | 10 |
| Covered Code | 6 |
And they must be respects to you when they come inserted, otherwise gives life to not valid values, and the breaking in of the occurrence is not allowed.
On this base of they give to you is possible to execute very many operations, from the insertion to the cancellation, the search intercrossed to the modification.
Its possible create of the procedures, the functions customer, all for one optimal management of the same one.
But all this allows to manage gives and values to you operated to you, that is puts into effect them; they are relatively little important in order to supply true and just an aid to a system of support to the decisions.
All this will come supplied through means of the Business Intelligence and the Datawarehouse, that they place however their bases in the database as soon as created.