What is the resource impact from normalizing a database?

Question

When taking a database from a relatively un-normalized form and normalizing it, what, if any, changes in resource utilization might one expect?

For example,

Answer 1

To underscore some points made by prior posters: Is you current schema really denormalized? The proper way (imho) to design a database is to:

• Understand as best you can the system/information to be modeled
• Build a fully normalized model
• Then, if and as you find it necessary, denormalize in a controlled fashion to enhance performance

(There may be other reasons to denormalize, but the only ones I can think of off-hand are political ones--have to match the existing code, the developers/managers don't like it, etc.)

My point is, if you never fully normalized, you don't have a denormalized database, you've got an unnormalized one. And I think you can think of more descriptive if less polite terms for those databases.