Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Analyser index recommendations

Analyser index recommendations

Scheduled Pinned Locked Moved Database
databasesql-serversysadmindebuggingtutorial
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    vkEE
    wrote on last edited by
    #1

    Hello all, I ran the trace file and then analysed this data in the Anaylser in SQL Server 2008. I have a table consisting of 2 million rows, and the analyser recommended 15 indexes. I am fairly new to this company and was not sure how to go about this. Is there some other way to figure which index would be really required? I have a field which is the Primary Key, a datetime field, a unique identified field. Thank you!

    M L 2 Replies Last reply
    0
    • V vkEE

      Hello all, I ran the trace file and then analysed this data in the Anaylser in SQL Server 2008. I have a table consisting of 2 million rows, and the analyser recommended 15 indexes. I am fairly new to this company and was not sure how to go about this. Is there some other way to figure which index would be really required? I have a field which is the Primary Key, a datetime field, a unique identified field. Thank you!

      M Offline
      M Offline
      Mycroft Holmes
      wrote on last edited by
      #2

      I usually try and pick the index that is going to hit the most granular field and create that first, rerun the analysis and repeat until satisfied with the performance. This often reduces the number of indexes actually required to gain significance performance gains.

      Never underestimate the power of human stupidity RAH

      1 Reply Last reply
      0
      • V vkEE

        Hello all, I ran the trace file and then analysed this data in the Anaylser in SQL Server 2008. I have a table consisting of 2 million rows, and the analyser recommended 15 indexes. I am fairly new to this company and was not sure how to go about this. Is there some other way to figure which index would be really required? I have a field which is the Primary Key, a datetime field, a unique identified field. Thank you!

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #3

        As Mycroft suggests, create the most granular index first. Indexes tend to be more useful when the distribution of data in the indexed column(s) is high. And create one index at a time and rerun the query to see how much performance improvement you've gained, if any. This way, if you find that the query has actually slowed down (which may happen sometimes), you can always disable or drop the index and proceed with the next one.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups