Mensys Online Shop
| Categorie: | Algemeen - Boeken | Van: | Apress |
| Meer informatie: | www.apress.com | Info-file: | big_front_BeginningD... |
Database design is not an exact science. Many are surprised to find that problems with their databases are caused by poor design rather than by difficulties in using the database management software. Beginning Database Design, Second Edition helps you ask and answer important questions about your data so you can understand the problem you are trying to solve and create a pragmatic design capturing the essentials while leaving the door open for refinements and extension at a later stage. » Lees meer... |  |
Alle prijzen zijn in Euro excl. BTW (19%, voor boeken 6%) en excl. verzendkosten.
E-mail of bel 023 548 20 20 voor licenties, upgrades en andere vragen.
Database design is not an exact science. Many are surprised to find that problems with their databases are caused by poor design rather than by difficulties in using the database management software. Beginning Database Design, Second Edition helps you ask and answer important questions about your data so you can understand the problem you are trying to solve and create a pragmatic design capturing the essentials while leaving the door open for refinements and extension at a later stage. Solid database design principles and examples help demonstrate the consequences of simplifications and pragmatic decisions. The rationale is to try to keep a design simple, but allow room for development as situations change or resources permit.•Provides solid design principles by which to avoid pitfalls and support changing needs•Includes numerous examples of good and bad design decisions and their consequences•Shows a modern method for documenting design using the Unified Modeling LanguageWhat you ll learn•Avoid the most common pitfalls in database design.•Create clear use cases from project requirements.•Design a data model to support the use cases.•Apply generalization and specialization appropriately.•Secure future flexibility through a normalized design.•Ensure integrity through relationships, keys, and constraints.•Successfully implement your data model as a relational schema.