• Replies 2 replies
  • Subscribers 337 subscribers
  • Views 41 views
  • Users 0 members are here
Related

UP_REBUILD_ALL_INDEXES schedule

Christopher Sherwood
$organization

All-

We've been running into some serious issues lately that I think may stem from our indexes being way too large and fragmented. In looking into a way to do this in a scheduled manner I found UP_REBUILD_ALL_INDEXES.

 

Does anyone use this procedure in a scheduled task, and if so, when?

 

Also, without looking at the code yet, does anyone know off hand if this fully rebuilds the indexes, or just reorganizes them?

 

Thanks,

Chris

  • Former Member
    Former Member $organization

    Hi Chris

    It rebuilds them all (offline), just like it says.  If your db is largeish, and heavily fragmented it can take a long time, and take indexes offline while it works on them.

    You certainly should be defragmenting indexes regularly though. Have a look at this forum thread for some other comments and suggestions from me....

    Ken

  • $organization

    Hi Chris,

     

    UP_REBUILD_ALL_INDEXES performs DBCC DBREINDEX; it rebuilds indexes, not reorganizes. We do scheduled index maintenance on a weekly basis; however, we use a procedure that only rebuilds if fragmentation is at a certain level ( I don’t remember the number offhand). If it is low enough, it reorganizes. This significantly speeds up the process and seems to work well; however, I did run UP_REBUILD_ALL_INDEXES shortly after our v11 migration to eliminate a couple of index problems we ran into.

     

    I can post the procedure we use if you are interested. I think there are others who have posted custom built procedures for this as well.

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christopher Sherwood
    Sent: Thursday, January 17, 2013 11:30 PM
    To: David Frederick
    Subject: [Tessitura Technical Forum] UP_REBUILD_ALL_INDEXES schedule

     

    All-

    We've been running into some serious issues lately that I think may stem from our indexes being way too large and fragmented. In looking into a way to do this in a scheduled manner I found UP_REBUILD_ALL_INDEXES.

     

    Does anyone use this procedure in a scheduled task, and if so, when?

     

    Also, without looking at the code yet, does anyone know off hand if this fully rebuilds the indexes, or just reorganizes them?

     

    Thanks,

    Chris




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!