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: All
Apr 16, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Keep Your Clustered Index's Weight Down

In SQL Server 7, a significant change was made to the way nonclustered indexes work when a clustered index exists on a table. In version 6.5, the nonclustered index used the rowid of each row to point back to the data. This meant that when you rebuilt a clustered index and reordered all the rows (thus changing the rowid) all the nonclustered indexes also had to be rebuilt. In version 7, a nonclustered index stores the key value of the clustered index as the method of retrieving the actual row. Therefore, as your clustered index gets wider, every nonclustered index will take up that much more space.
Joseph Lax
 
Comment and Contribute

 

 

 

 

 


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

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date