<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Principles of Modeling: Avoid Redundancy</title><link>http://sqlblog.com/blogs/hugo_kornelis/archive/2012/05/05/principles-of-modeling-avoid-redundancy.aspx</link><description>In 1994, I learned a method for data modeling that is based on three principles. I immediately knew that these principles should embraced by anyone who does any data modeling or process modeling. Or almost any other job, for that matter. I have described</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Principles of Modeling: Avoid Redundancy</title><link>http://sqlblog.com/blogs/hugo_kornelis/archive/2012/05/05/principles-of-modeling-avoid-redundancy.aspx#43509</link><pubDate>Wed, 23 May 2012 08:03:16 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:43509</guid><dc:creator>me</dc:creator><description>&lt;p&gt;Nice article. I think reduce the redudant work.&lt;/p&gt;
</description></item></channel></rss>