Friday, September 10, 2010
Banner

Announcements
 

Discussion Group Login Minimize
  


Users Online Minimize
Membership Membership:
Latest New User Latest: jguy
New Today New Today: 0
New Yesterday New Yesterday: 1
User Count Overall: 2397

People Online People Online:
Visitors Visitors: 1071
Members Members: 0
Total Total: 1071

Online Now Online Now:
  

Archive Minimize
Partners Minimize

InfoAdvisors partners with

 
embt.png
 
 
Microsoft
Sybase
Telelogic
 
We can help you evaluate and successfully implement our partners' products
 


Welcome... Minimize

Welcome to InfoAdvisors' website dedicated to information technology processes.  You'll find subscriber-written articles on UML, data management, data modeling, process modeling, ITIL, information governance, as well as materials to help you improve your information management resources.



Karen Lopez: Musings on Data, Process, and Architecture Minimize
Dec 7

Written by: Karen Lopez
Fri, 07 Dec 2007 16:03:16 GMT 

An anonymous blogger has started writinga series of posts of his experiments with database design and performance.  His profile describes him as "A Seattle database guy who works at start ups."

In the last article the performance impact of joins was shown.  This one will demonstrate cases where denormalized joins are a bit faster, as will the third article with larger data volumes.  The fourth article, the most interesting one, will show where a denormalized data model can be 50 times faster than a normalized data model. 

Here are the tables that will be involved in the sql.  The normalized ProductSmall table has a 100 million rows and is about 0.67 gig. 

What I appreciate about his posts is the fact that he is supporting his positions with actual tests.  So far his two blog posts have focused on very large tables (more than a million rows) and the impact of memory usage.

I'd also like to see him post about working with smaller data volumes.  For instance, I work at times with new developers who tell me that our database or table is "very large" at 4,000 rows and needs a great deal of denormalization for performance reasons.  I usually ask them to run tests similar to what the DBScience guy is doing to show me all the great benefits of combining 6 tables into one table with a total of 10,000 rows.

Check out his blog as he adds articles. http://dbscience.blogspot.com/

Tags:

Your name:
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Security Code
Enter the code shown above in the box below
Add Comment   Cancel 
InfoAdvisors Calendar List Minimize

 Month view   Week view   List view    

  Minimize

Copyright 2006-8 InfoAdvisors, Inc.