Re: Indexes on SQL Server 7.0
- From: Hugo Kornelis <hugo@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 23:34:23 +0200
On 26 Mar 2007 21:29:32 -0700, othellomy@xxxxxxxxx wrote:
Doesn't seem to be to be very beneficial to have an index that only
includes the primary key. So for example I'm thinking of creating an
index for MatterConflicts that includes the fields: MatterConflicts,
Matters, and HitMatters.
no. Don't use composite indexs as they seldom are useful.
Hi othellomy,
Do you have any source for that sweeping statement?
AFAIK, composite indexes can be VERY useful. For queries that filter or
join on two or more columns, a composite index is much better than
seperate indexes on the individual columns.
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
.
- Prev by Date: Re: Update Status Field after Expiry Date
- Next by Date: Re: SQL Server Problem
- Previous by thread: SQL Server Problem
- Next by thread: Re: data length more than ...
- Index(es):
Relevant Pages
|
