Communiquez avec les autres et partagez vos connaissances professionnelles

Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.

Suivre

How to build a better database design?

user-image
Question ajoutée par CALLIXTE NKURIKIYIMANA
Date de publication: 2015/08/17
Muhammad Usman Jalil
par Muhammad Usman Jalil , System Analyst and DBA , KPTC (Kuwait Public Transport Company)

Try to normalize the tables as much you can....And then do all your programming in your Stored Procedures avoid much programming at application back-end level....this will reduce your headache in future if you update your system constantly.....or you are eager to use the system on multi platforms....

Once you have did you programming you can build on your stored procedures....DAL (Data Access Layer), BOL / BLL (Business Object / Logic Layer).......then you can compile them to run-time assemblies and can you use them on multi platforms....

subhas k
par subhas k , Technology Lead , Wells Fargo(Investment/Capital/Share market/Finance applications)

Understand the FD exactly.

Achieve TD from FD.

Imagine UI with respect to DB side by side.

Identify importance of work flow b/w different modules.

Identify strong FD with respect to Keycolumns.

Derive tables with help of FD and TD.

Finally think about the relations, check constraints, normalization

Zemene Arega
par Zemene Arega , IOCC marketing coordinate and system expert , Ethiopia Airline

First  follow the rules that, how we build better database. As i know, the following articles are so important to build a database: Ø  Know is the nature of the application Ø  Break your data into logical pieces, make life simpler Ø  Treat duplicate non-uniform data as your biggest enemy Ø  Watch for data separated by separators Ø  Watch for partial dependencies Ø  Choose derived columns preciously Ø  Do not be hard on avoiding redundancy, if performance is the key Ø  Multidimensional data is a different beast altogether Ø  Centralize name value table design

 

Ø  For unlimited hierarchical data self-reference PK and FK