dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Beginner
Sep 11, 1998

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Avoid Monolithic Tables in SQL Server

You can improve SQL server performance if you avoid creating tables in a monolithic fashion. By monolithic I mean tables that have dozens and dozens of fields that are not often used together. Some shops lump all data associated with a key field (or fields) into one table. A better structure is to make multiple tables, each containing only the relevant data that is used together, with each table having the same key field. For example, instead of using one "Big Table," use three smaller ones:
 
BIG_TABLE   --becomes-- PART_TABLE	MTD_TABLE	YTD_TABLE
part_num (key)		part_num (key)	part_num (key)	part_num (key)	
-------			-------		-------		-------
part_desc		part_desc	mtd_ship	ytd_ship
part_wt			part_wt		mtd_sales	ytd_sales
part_uom		part_uom	mtd_return	ytd_return
.
.
.
mtd_ship
mtd_sales
mtd_return
.
.
.
ytd_ship
ytd_sales
ytd_return

Joe Karbowski
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date