<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on See SQL Server graphical execution plans in action ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-239495/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-06-19T04:33:57-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2332606]]></link>
        <description><![CDATA[That would be the sound of my head as my mind is expanding.  :-PThanks for the information about indexes Tim.  Finally, index articles and discussions are making more sense.  It feels good to know that I no longer have to fear them, however just my introduction has me asking dozens of new questions.  Thanks for opening the door.  Again, I look forward to your future articles.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2332606]]></guid>
        <dc:creator><![CDATA[thisisfutile]]></dc:creator>
        <pubDate>Fri, 05 Oct 2007 09:35:21 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Yes, it makes sense.]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2332552]]></link>
        <description><![CDATA[Thanks for the explanation.  Now Figure E makes even more sense to me because I didn?t understand that relationship between clustered and non-clustered indexes.  Also, I referenced your comment &quot;when a clustered index is added to a table, any nonclustered indexes on that table will need to be rebuilt&quot; in my previous post and the NC index being a pointer explains why the NC index(es) on the table need rebuilt after a clustered index is defined.  I love it when the fog of confusion begins to lift!  ]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2332552]]></guid>
        <dc:creator><![CDATA[thisisfutile]]></dc:creator>
        <pubDate>Fri, 05 Oct 2007 09:06:04 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[RE: See SQL Server graphical execution plans in action]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2331188]]></link>
        <description><![CDATA[This was really a good articale Tim. Thanks for providing a good starting point on Query optimization. This may be just another article for the seasoned DBAs on TR but a great insite for a novice like me. I will be waiting for your take on understanding performance of Joins.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2331188]]></guid>
        <dc:creator><![CDATA[jayrajvakil]]></dc:creator>
        <pubDate>Wed, 03 Oct 2007 11:45:04 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Re:  I second that]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2331008]]></link>
        <description><![CDATA[Have a look at this articles on TR (not written by me) that cover indexes.  Let me know if these answer your questions.  If not, I'd be happy to include an article that details the differences between the two types of indexes.Indexing SQL Server relational databases for performancehttp://articles.techrepublic.com.com/5100-6313_11-5148062.html Database Optimization: Increase query performance with indexes and statisticshttp://articles.techrepublic.com.com/5100-6313_11-5146588.html]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2331008]]></guid>
        <dc:creator><![CDATA[chapman.tim@...]]></dc:creator>
        <pubDate>Wed, 03 Oct 2007 08:24:30 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I second that]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330867]]></link>
        <description><![CDATA[I've only recently started following your stuff..it helps me out a bit here and there.I second the suggestion of doing some stuff on Clustered and non-clustered indexes.In theory..i can recite what the books say..but as I've inherited the DB, in practice (and very little practice at indexing)..they make my head hurt!]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330867]]></guid>
        <dc:creator><![CDATA[Shellbot]]></dc:creator>
        <pubDate>Wed, 03 Oct 2007 05:59:52 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Thanks]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330286]]></link>
        <description><![CDATA[I'm happy to hear that you like my articles.  I don't think I have any articles that outline the difference between the two types indexes.  Basically, a clustered index orders the data in the table based upon how you define that index.  Searching with a clustered index is great for range searches based upon the index key because the data will be right next to each other.  You can only have one clustered index per table.  A NC index, on the other hand, uses the same type of index structure as a clustered index, but does not sort the data in order.  Instead, it uses a row pointer to the location of the data page that it needs to return data, and uses the clustered index key as a tool to locate that data.  You can have up to 255 (I think) nonclustered indexes on a table.Does that make sense?]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330286]]></guid>
        <dc:creator><![CDATA[chapman.tim@...]]></dc:creator>
        <pubDate>Tue, 02 Oct 2007 09:12:25 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Question:  Indexes]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330247]]></link>
        <description><![CDATA[I'm still following (and enjoying) this series Tim.  Thanks again for more good info.  There are probably many SQL Server DBAs who know detail like you do and may gather little or nothing from this series, but this is the perfect mix of general and detail info to keep my interest and I find it extremely valuable.  I'm looking forward to the next article.Question:  If you haven't done it in another article already, could you expand on Clustered and non-clustered indexes?  If you have, could you point me to your article(s)?  I'm curious because while I work closely with a fairly large database, I didn't have anything to do with setting it up.  When it comes to indexes, I still have a lot to learn and this article represents my first peek into the affects of indexes on a table (the date column was a good example...I tried the Select statement with and without the index present and the difference was very noticeable).  I was especially curious when you said that adding a clustered index to a table means that all non-clustered indexes need to be rebuilt.  If you plan to discuss this later, as usual, I'll continue to follow this series and wait patiently.Thanks,Gabe]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-239495-2330247]]></guid>
        <dc:creator><![CDATA[thisisfutile]]></dc:creator>
        <pubDate>Tue, 02 Oct 2007 08:27:06 -0700</pubDate>
    </item>
    </channel>
</rss>

