SQL Saturday presentation

  • I'm looking at a topic for SQL Saturday. It's going to be held in conjunction with a .net Code Camp, so there will be a mix of both DB and .net developers wandering around and I thought a basic indexing presentation might be interesting:

    What makes an index tick and why do they make your queries faster? To answer that question, this session will look at how SQL Server stores index data and how statistics help the optimizer determine when to use an index. We'll look at a few cases where the optimizer either doesn't use an index or uses it inconsistently, and explain how to address them. Finally we tie everything together with some recommendations on how to identify and implement a good index.

  • I like that description. That's good.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Thought up a good cheezy title this morning: "The new i6 (Investigation Into Index Internals, Including Implementation)"

  • Chad Crawford (7/29/2011)


    Thought up a good cheezy title this morning: "The new i6 (Investigation Into Index Internals, Including Implementation)"

    What's I6????

  • What makes an index tick and why do they make your queries faster.

    Is a title that would attract myself, as far as the I6 reference, would skip over the thought of going simply because I did not know what I6 was/represented/might be too specialized a subject.

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • Ninja's_RGR'us (7/29/2011)


    Chad Crawford (7/29/2011)


    Thought up a good cheezy title this morning: "The new i6 (Investigation Into Index Internals, Including Implementation)"

    What's I6????

    Investigation Into Index Internals, Including Implementation

    i6 also kind of sounds like Intel's i5 and i7 processor line or a mathematical equation (i to the 6th power).

    It was an attempt to dress up what might otherwise sound like a boring typical topic... which I guess it is anyway 🙂

  • Chad Crawford (7/29/2011)


    Ninja's_RGR'us (7/29/2011)


    Chad Crawford (7/29/2011)


    Thought up a good cheezy title this morning: "The new i6 (Investigation Into Index Internals, Including Implementation)"

    What's I6????

    Investigation Into Index Internals, Including Implementation

    i6 also kind of sounds like Intel's i5 and i7 processor line or a mathematical equation (i to the 6th power).

    It was an attempt to dress up what might otherwise sound like a boring typical topic... which I guess it is anyway 🙂

    Ok my guess was interstate 6.... which made no sense at all!

  • bitbucket-25253 (7/29/2011)


    What makes an index tick and why do they make your queries faster.

    Is a title that would attract myself, as far as the I6 reference, would skip over the thought of going simply because I did not know what I6 was/represented/might be too specialized a subject.

    I planned to put the full line into the title: "The new i6 (Investigation Into Index Internals, Including Implementation)"

    Is it too vague? Does the alliteration using I's not adequately map to the i6? If the "joke" is lost, it's way not worth it.

    Does the topic sound appropriate for SQL Saturday? There's another submitted about index maintenance, which would have some overlap, but I think we're headed different directions so it should be ok.

    Thanks for your comments all - I appreciate your help!

  • Chad Crawford (7/29/2011)


    bitbucket-25253 (7/29/2011)


    What makes an index tick and why do they make your queries faster.

    Is a title that would attract myself, as far as the I6 reference, would skip over the thought of going simply because I did not know what I6 was/represented/might be too specialized a subject.

    I planned to put the full line into the title: "The new i6 (Investigation Into Index Internals, Including Implementation)"

    Is it too vague? Does the alliteration using I's not adequately map to the i6? If the "joke" is lost, it's way not worth it.

    Does the topic sound appropriate for SQL Saturday? There's another submitted about index maintenance, which would have some overlap, but I think we're headed different directions so it should be ok.

    Thanks for your comments all - I appreciate your help!

    That could work as a title that way. But the joke was a little lost on me. Maybe need a few more eyes to see a good pattern.

  • Ninja's_RGR'us (7/29/2011)


    That could work as a title that way. But the joke was a little lost on me. Maybe need a few more eyes to see a good pattern.

    Did you mean eyes or I's. 😛 Just kidding - I know what you meant, just seemed really funny the first time reading it.

    I-15 runs past the venue and has been under construction/maintenance for what seems like 10 years. If I could come up with a longer sentance I could use "I-15 Construction", but it would be incredibly forced and ugly.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply