Tim,
I disagree with you in that you don't really have to get "extreme"
before the extra indexing will hurt you. On every insert or update, your
database will have to go through every index and update it too. As you
say, if your database is fairly static, it won't hurt you much, but my
point is that you won't need to do very many inserts / updates before you
notice that they are slow in processing. For as much as I gripe about
Microsoft, I must say that their Index Tuning Wizard is an excellent tool
for those using SQL Server 2000. It uses your real-world database traffic
to decide which indexes are useful, which are unnecessary, and which
should be added.
Thanks,
Eric
"Raster, Tim" <[EMAIL PROTECTED]>
09/08/2003 12:32 PM
Please respond to sql
To: SQL <[EMAIL PROTECTED]>
cc:
Subject: RE: I need some indexing advice
Yup. And look for opportunities to index multiple fields within an
index, if both are commonly searched.
Others may disagree with me here, but I usually follow the philosophy
of, "When in doubt, index it." It's usually only in very extreme
(highly transactional) cases that the index will hurt. If your database
is fairly static, then index the crap out of it.
-----Original Message-----
From: Phillip B [mailto:[EMAIL PROTECTED]
Sent: Monday, September 08, 2003 11:25
To: SQL
Subject: Re: I need some indexing advice
I should have also mentioned that part of the where clause is what brand
they sell. Should I consider indexing the brand fields as well since
that is
a common search criteria?
Phillip B.
www.LoungeRoyale.com
www.FillWorks.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/lists.cfm?link=t:6
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:6
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=<:emailid:>.<:userid:>.<:listid:>
Signup for the Fusion Authority news alert and keep up with the latest news in
ColdFusion and related topics.
http://www.fusionauthority.com/signup.cfm
