Tough Consolidation of Rows

  • I am pretty sure he is just suffering from heap fragmentation !!!

    1 million rows is not supposed to bring the server down even with the subqueries we wrote !!!

    My bet is that after he get ANY clustered index in things will change DRAMATICALLY

     


    * Noel

  • Well duh!!!

    I bet more ram, faster drives and faster/more cpus could help too .

  • ram, faster drives and faster/more cpus  all cost $$

    an index is FREE


    * Noel

  • FREE... but also much easier to implement, not to mention the right thing to do here .

  • Sorry got caught up with other things.

    Take the other index's off and maket he 1 clustered Noel?

  • No just created the clustered in on those 2 fields. No need to change anything else at the moment.

  • For the moment don't remove the others Just add the clustered!!

    Like:

    create unique clustered index IX_MY_UC on Yourtable(NumSet1,NumSet2) with fillfactor = 90

     


    * Noel

  • Running now......

  • Man you are fast!!


    * Noel

  • Yup... leaving fast here too (1 hour early). I just I'll be able to do that when I work for you .

    Ok now I'm really gone.

  • Just stopped it on 10 minutes, no results, going to add the fill factor.

  • Have a good weekend!!

    We'll see about that!

     


    * Noel

  • How much memory do you have on the server ?

     


    * Noel

  • Going to stop and start sql services and free up some resources,

    I think there is a gig, am going to go check.

  • one more thing run UPDATE STATISTICS YourTableName WITH FULLSCAN

    and Try again

    if still slow can you post your execution plan ?

     


    * Noel

Viewing 15 posts - 16 through 30 (of 33 total)

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