Building a Strong Data

By Timothy Dyck  |  Posted 2003-03-10 Print this article Print

Architecture"> Building a Strong Data Architecture

Keep data available
  • Portal, Web-based and mobile application deployments keep employees in close contact with data.
  • Database replication techniques allow for broad data distribution while enforcing data quality rules.
  • Security should be implemented as close to the data as possible using row- and column-level permissions.

    Keep data accurate
  • Maintain a centralized, consistent data dictionary.
  • Try to initially create departmental databases by building subsets of larger operational databases.
  • Enforce business rules at all points of data entry using shared business logic.

    Keep data in context
  • When possible, fold warehouse and analysis tasks into operational databases to allow all data to be manipulated in one place.
  • OLAP, data mining, data visualization and statistical analysis are all highly effective (although underused) techniques for understanding data.
  • Web services allow data from enterprise resource planning and other vertical applications to be integrated into line-of-business applications far more easily than ever before.

    Timothy Dyck is a Senior Analyst with eWEEK Labs. He has been testing and reviewing application server, database and middleware products and technologies for eWEEK since 1996. Prior to joining eWEEK, he worked at the LAN and WAN network operations center for a large telecommunications firm, in operating systems and development tools technical marketing for a large software company and in the IT department at a government agency. He has an honors bachelors degree of mathematics in computer science from the University of Waterloo in Waterloo, Ontario, Canada, and a masters of arts degree in journalism from the University of Western Ontario in London, Ontario, Canada.

    Submit a Comment

    Loading Comments...
    Manage your Newsletters: Login   Register My Newsletters

    Rocket Fuel