|
Logical data base design is an iterative process. In accumulation
to a starting point, it has an almost endless number of refinements
and requires a great deal of thought, planning, and collaboration.
To implement one successfully, it will involve a lot of tools.
Paying attention at the beginning of the project will ensure
that its’ applications will not only be easy to use
but also easy to maintain and long lasting.
To use any product efficiently, it will requires a thorough
understanding of entity-relationship (ER) diagram concepts
and a clear understanding of the data you want contained in
the diagram. If you are starting from scratch, you may want
to use a data modular. Technically, a database is collections
of names and numbers, of dates and dollar amounts. One should
think of a database as more than just that. One’s data
is a record of customer interaction; which is the most valuable
commodity. Unfortunately, many times data is in disarray.
Many companies' data usage is foreseen as what it could be,
sometimes with outdated or ghastly systems. One should work
to obtain a system that ensures a database overhaul provides
you with a database that not only track transactions, but
can increase your efforts' speed to market; allows you a higher
level of targeting and segmenting sophistication, and helps
you reduce waste and any number of other benefits.
First you must think through the details. A database should
be built to fit your needs. You should be sure the database
you create will not obtain useless information or data you
do not understand. It is not wise to start your design alone,
one should turn to people with training and specialized software.
Some times you may end up with that “unwanted”
data, but do not make ridding of that problem first on your
to-do list. First design your database, then quickly clean
and standardize the data, and finally perform merge/purge,
other appends.
To have a good system, talk to the people who'll be using
it. Users are liable to be a company's marketing department,
but a segment of the unearthing process should be devoted
to finding out all the users in a company. Many companies
interview their internal data users to find out their big
needs, pains and concerns before moving ahead with its database
rebuild. The user input is the access to the database. The
database should be accessible online. If you have data overhaul,
you can increase mail efficiency, thus easily combining your
data with outside sources.
Copyright
© 2005 Database Design Information. Send comments here. |
 |
