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: Intermediate
Apr 14, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Primary Key Should Not be Clustered

By default, when you define a primary key in the create table statement, it uses a clustered index. However, a clustered key is best used to support queries that return more than one row. For example, if you have a date field that is often used to return activity for a range of days, a clustered index will be much faster than a nonclustered one. To preserve your clustered index for other columns, you can add the keyword nonclustered to the primary constraint definition; that is, constraint pkaccount primary key nonclustered (acctid).
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