Let us remember that one of the objectives of the normalization of the
tables is that the operations of update, elimination, insertion are easy
to do.

That the information has the smaller possible redundancy, so that these
operations are easy to do. Obvious we will have redundancy but it will be
controlled.

The database engine that we use will be the one in charge to optimize the
SQL that we write, although also depends on as we write the SQL.

good there are other things that we must take into account, but the
initial phase is the design of the tables.

Greetings.

Ext. 225 Escribio :-)

>
>
>
>
> Martijn,
>
> > What "fastest" - table design shouldn't be about speed,
> but about > consistency and normalized data structures.
>
> The reality is never as black and white as you've suggested.
>
> Admittedly, a database design should meet the criteria you outlined.
>
> However, there are allowance/situations where *some* denormalization is
> appropriate and beneficial.
>
>
> --
> Sean Leyne
>
> Want to support Firebird development?
> Become a member of the FirebirdSQL Foundation!
> http://www.firebirdsql.org/foundation
>
>
>
>
>
>
>
>
>
> Yahoo! Groups Sponsor
>
>
> ADVERTISEMENT
>
>
>
>
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

--
Carlos Chávez
AG Software, S.A.
776-8344
267-3007