Our Recommendations :-
Follow IT FB Page

what is Database design and its importance

Avatar 37a3bd7bc7328f0ead2c0f6f635dddf60615e676e6b4ddf964144012e529de45 Uma asked almost 3 years ago

    0       0 Answer Now Comment Report
4 Answers
Avatar 37a3bd7bc7328f0ead2c0f6f635dddf60615e676e6b4ddf964144012e529de45 veeru answered over 2 years ago

Database design is the process of producing a detailed data model of a database. This data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a data definition language, which can then be used to create a database. A fully attributed data model contains detailed attributes for each entity.

    0       0 Comment Report
Important Note – Preparing for IT?
CAKART provides Indias top faculty each subject video classes and lectures – online & in Pen Drive/ DVD – at very cost effective rates. Get video classes from CAKART.in. Quality is much better than local tuition, so results are much better.
Watch Sample Video Now by clicking on the link(s) below – 
For any questions Request A Call Back  
Avatar 37a3bd7bc7328f0ead2c0f6f635dddf60615e676e6b4ddf964144012e529de45 Aarti Vadnerkar answered almost 3 years ago

The Importance of Good Database Design A good database design is crucial for a high performance application, just like an aerodynamic body is important to a race car. If the car doesn't have smooth lines, it will produce drag and go slower. Without optimized relationships, your database won't perform as efficiently as possible. Thinking about relationships and database efficiency is part of normalization. Normalization refers to the process of structuring data in order to minimize duplication and inconsistencies. Beyond the issue of performance is the issue of maintenanceyour database should be easy to maintain. This includes only storing a limited amount (if any) of repetitive data. If you have a lot of repetitive data and one instance of that data undergoes a change (such as a name change), that change has to be made for all occurrences of the data. To eliminate duplication and enhance your ability to maintain the data, you might create a table of possible values and use a key to refer to the value. That way, if the value changes names, the change occurs only oncein the master table. The reference remains the same throughout other tables. For example, suppose you are responsible for maintaining a database of students and the classes in which they're enrolled. If 35 of these students are in the same class, let's call it Advanced Math, this class name would appear 35 times in the table. Now, if the instructor decides to change the name of the class to Mathematics IV, you must change 35 records to reflect the new name of the class. If the database were designed so that class names appeared in one table and just the class ID number was stored with the student record, you would only have to change 1 recordnot 35in order to update the name change. The benefits of a well-planned and designed database are numerous, and it stands to reason that the more work you do up front, the less you'll have to do later. A really bad time for a database redesign is after the public launch of the application using italthough it does happen, and the results are costly. So, before you even start coding an application, spend a lot of time designing your database. Throughout the rest of this chapter, you'll learn more about relationships and normalization, two important pieces to the design puzzle.

    0       0 Comment Report
Open uri20170510 32134 1uwcnoc?1494421631 Shubhangi Jain answered almost 3 years ago

**Database design** is the process of producing a detailed data model of a database. This data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a data definition language, which can then be used to create a database. A fully attributed data model contains detailed attributes for each entity. > The Importance of Good Database Design A good database design is crucial for a high performance application, just like an aerodynamic body is important to a race car. If the car doesn't have smooth lines, it will produce drag and go slower. Without optimized relationships, your database won't perform as efficiently as possible. Thinking about relationships and database efficiency is part of normalization. Normalization refers to the process of structuring data in order to minimize duplication and inconsistencies. Beyond the issue of performance is the issue of maintenanceyour database should be easy to maintain. This includes only storing a limited amount (if any) of repetitive data. If you have a lot of repetitive data and one instance of that data undergoes a change (such as a name change), that change has to be made for all occurrences of the data. To eliminate duplication and enhance your ability to maintain the data, you might create a table of possible values and use a key to refer to the value. That way, if the value changes names, the change occurs only oncein the master table. The reference remains the same throughout other tables. For example, suppose you are responsible for maintaining a database of students and the classes in which they're enrolled. If 35 of these students are in the same class, let's call it Advanced Math, this class name would appear 35 times in the table. Now, if the instructor decides to change the name of the class to Mathematics IV, you must change 35 records to reflect the new name of the class. If the database were designed so that class names appeared in one table and just the class ID number was stored with the student record, you would only have to change 1 recordnot 35in order to update the name change. The benefits of a well-planned and designed database are numerous, and it stands to reason that the more work you do up front, the less you'll have to do later. A really bad time for a database redesign is after the public launch of the application using italthough it does happen, and the results are costly. So, before you even start coding an application, spend a lot of time designing your database. Throughout the rest of this chapter, you'll learn more about relationships and normalization, two important pieces to the design puzzle.

    0       0 Comment Report
Avatar 37a3bd7bc7328f0ead2c0f6f635dddf60615e676e6b4ddf964144012e529de45 lochan answered almost 3 years ago

Database design refers to the activities that focus on the design of the database structure that will be used to store and manage end-user data. A database that meets all user requirements does not just happen; its structure must be designed carefully. Even a good DBMS will perform poorly with a badly designed database. Proper database design requires the designer to identify precisely the database expected use. Designing a transactional database recognizes accurate and consistent data and operational speed. The design of a data warehouse database recognizes the use of historical and aggregated data. Designing a database to be in a centralized, single-user environment requires a different approach from that used in the design of a distributed, multi-user environment. A well-designed database facilities data management and generates accurate and valuable information. A poorly designed database is likely to become a breeding ground for difficult-to-trace errors that may lead to bad decision making and bad decision making can lead to the failure of an organization. Thanks

    0       0 Comment Report
Get Notifications
Videos
Books
Notes
Loading
SIGN UP
Watch best faculty demo video classes

These top faculty video lectures will
help u prepare like nothing else can.