Indexes on large tables

  • I wish. This is our development box, which has limited space - not only that, but our SA doesn't allow DBO's like myself manage any files. Or do much of anything for that matter.

  • Hard drives are cheap. Get IT/SA to add some space to the dev system.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • just a point but 70million rows isn't that big!

    You say you don't have the ability to use the tuning advisor - so what? you can still generate estimated query plans and/or generate query plans and io stats - or you could use profiler to capture query plan information. In sql 2005 the dmvs contain masses of information including missing indexes, poor queries by cpu, io, etc. etc.

    if you look on my web site I did some work on large(ish ) tables and index analysis including using clustered indexes etc. http://www.grumpyolddba.co.uk

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • which reminds me, any columns SQL generates statistics on (_WA_sys*) are possibly candidates for indexes as the optimiser has obviously decided it needs info on those columns.

    ---------------------------------------------------------------------

Viewing 4 posts - 16 through 18 (of 18 total)

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