I've been developing RDBMS applications as a consultant for large corporations for some 15+ years and often I come in at some mid-way point in the database design by junior developers and management. The argument to use surrogate keys is often the first one I have to make as I look over the design that I'm supposed to take the "technical lead" on implementing. It usually takes several "horror" stories of lessons learned on legacy systems in my past experience and even then, management *reluctantly* goes along with my suggestion. This often happens at the expense of other potential suggestions I might like to make because any good consultant has to "pick his/her battles" so as not to seem like a non-team player. This article (as long asit's available) will remain as a favorite link in my browser at-the-ready for any future arguments I may have to make in favor of surrogate keys.