Why data updating is important

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.

But here in the real world of development we make changes to designs and models all day long.

We need to estimate the cost of change, measure the impact of that change and make changes.

She is a frequent speaker, blogger and panelist on data quality, data governance, logical and physical modeling, data compliance, development methodologies and social issues in computing.

Karen is an active user on social media and has been named one of the top 3 technology influencers by IBM Canada and one of the top 17 women in information management by Information Management Magazine.

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.

why data updating is important-87

I see this uptick in inquiries as a good indicator of job stability for data professionals. If anything, I’m hoping it means that the pendulum has swung a bit back to center from “software is everything” mentalities. If you hire the right kind of architect, he or she should be able to do that sort of training if you budget time for them to do that.

Yes, one day North America may collide with Asia to form , but if your database somehow survives that long at least you won't be around for the meeting on how to restructure your tables. Now, If using ENUM were our only option for representing what continent a country belonged to, we could all move on to debating the merits of No SQL or whether Git was better than SVN, or why your favorite framework sucks.

But there is a superior option to ENUM in most cases: the lookup/joined/reference table.

I need to be able to generate changes to databases without a lot of hand scripting and I can’t drop the database and recreate it on a regular basis.

I have to do that while supporting multiple versions of the same DBMS or multiple types of DBMSs.

Leave a Reply