﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Performance Tuning  / basic guidelines on creating Indexes / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 05:47:57 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: basic guidelines on creating Indexes</title><link>http://www.sqlservercentral.com/Forums/Topic684771-360-1.aspx</link><description>[quote][b]GilaMonster (3/27/2009)[/b][hr][quote][b]Krishna (3/27/2009)[/b][hr]1.) There should be at least one clustered index for a table which should be Narrow, ever-increasing, unique[/quote]At least one?[/quote]OMG what am I saying- only one[quote][quote]5.)Think about Covering indexes to cover all the columns retrieved in your query[/quote]Not all queries can be covered, not all queries should be covered. Sometimes the cons outweigh the pros. (Think of the size of a very large covering index)[/quote]Definitely not there are cons as well, but gave a basic idea[quote][quote]6.) Order of Index columns pretty important as SQL server maintains indexes only on the lading edge of the indexed columns[/quote]I assume you mean statistics on the leading column?[/quote]yes, ahh may be am smoking something when i was typing. :-)thanks for pointing it out. next time should be careful while typing.....</description><pubDate>Fri, 27 Mar 2009 14:13:29 GMT</pubDate><dc:creator>maechismo_8514</dc:creator></item><item><title>RE: basic guidelines on creating Indexes</title><link>http://www.sqlservercentral.com/Forums/Topic684771-360-1.aspx</link><description>[quote][b]Krishna (3/27/2009)[/b][hr]1.) There should be at least one clustered index for a table which should be Narrow, ever-increasing, unique[/quote]At least one?[quote]5.)Think about Covering indexes to cover all the columns retrieved in your query[/quote]Not all queries can be covered, not all queries should be covered. Sometimes the cons outweigh the pros. (Think of the size of a very large covering index)[quote]6.) Order of Index columns pretty important as SQL server maintains indexes only on the lading edge of the indexed columns[/quote]I assume you mean statistics on the leading column?There's a lot, lot more to order of columns that that. I wrote two blog posts on just that topic[url]http://sqlinthewild.co.za/index.php/2009/01/19/index-columns-selectivity-and-equality-predicates/[/url][url]http://sqlinthewild.co.za/index.php/2009/02/06/index-columns-selectivity-and-inequality-predicates/[/url]</description><pubDate>Fri, 27 Mar 2009 14:05:05 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: basic guidelines on creating Indexes</title><link>http://www.sqlservercentral.com/Forums/Topic684771-360-1.aspx</link><description>[quote][b]swmsan (3/26/2009)[/b][hr]Dear All,          Can anyone give me basic guidelines on creating Indexes...pls.Thanks in advance.[/quote]Let me give a shot too:1.) There should be atleast one clustered index for a table which should be Narrow, ever-increasing, unique2.) Try think of creating clustered indexes on the ones which are used in range queries and the ones which are used for ORDER by clause3.) Frequently updated columns and non-unique columns are not a good choice4.) Non- clustered indexes when needed but be careful about the number of indexes . more number of indexes more performance overhead on your table for DML operations5.)Think about Covering indexes to cover all the columns retrieved in your query6.) Order of Index columns pretty important as SQL server maintains indexes only on the lading edge of the indexed columns7.) Give consideration about fill factor too when creating indexes, inappropriate fill factor may lead to index fragmentation</description><pubDate>Fri, 27 Mar 2009 07:12:05 GMT</pubDate><dc:creator>maechismo_8514</dc:creator></item><item><title>RE: basic guidelines on creating Indexes</title><link>http://www.sqlservercentral.com/Forums/Topic684771-360-1.aspx</link><description>That's a very broad topic. Here are a few of my personal pointers1) Pick the clustered index first and pick it carefully2) Keep the clustered index as narrow as practical (note: not as narrow as possible, narrow means smaller data types and fewer columns)3) Usually the most frequently accessed data path is the best place for the clustered index since that's where the data is stored.4) Create nonclustered indexes only when you know you need them. Create as few as possible and keep them as narrow as practical too.5) Test, test, test, test, test, test6) Test some more.</description><pubDate>Fri, 27 Mar 2009 06:05:00 GMT</pubDate><dc:creator>Grant Fritchey</dc:creator></item><item><title>basic guidelines on creating Indexes</title><link>http://www.sqlservercentral.com/Forums/Topic684771-360-1.aspx</link><description>Dear All,          Can anyone give me basic guidelines on creating Indexes...pls.Thanks in advance.</description><pubDate>Thu, 26 Mar 2009 23:09:40 GMT</pubDate><dc:creator>Joy Smith San</dc:creator></item></channel></rss>