Why data updating is important

I wrote about this data architect hiring dilemma previously. The iterative process of doing logical models, having multiple physical models based on them, making changes to them (either because you are in development or because you have a new requirement) is how projects work in the real world.

Many of the less expensive tools allow you to reverse engineer a database and forward engineering a full database.

At first glance it seems like an efficient solution for declaring a set of permitted values from which only one can be chosen for each record.

A good example is a having a table of countries with a 'continent' column: every country belongs to a continent and the seven continents aren't likely to change anytime soon.

The less expensive ones either don’t’ do any of that, or they don’t easily support the iterative process of real life modeling and design.

I also need to be able to produce reports, images and interactive versions of the data models.

She is a Microsoft SQL Server MVP, specializing in data modeling and database design.

She’s an advisor to the DAMA, International Board and a member of the Advisory Board of Zachman, International.I also need to be able to share the models in formats that can be easily consumed by dozens of other modeling and development tools.Most of the lesser tools don’t have these shiny features.In a purely designed database these values would be divested into an extra entity or Reference Table called 'status' in order to achieve database normalization.So, with reference tables available as an option to represent an enumeration, let's look at why the ENUM data-type is evil: Male/Female, Mr/Mrs/Ms, Africa/Asia/etc: these bits of text that people use ENUM columns for are .Many of the real data modeling tools have features geared toward collaborating with other team members.

Tags: , ,