Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

Reorganze index and Statistics Expand / Collapse
Posted Thursday, March 28, 2013 8:53 AM



Group: General Forum Members
Last Login: Today @ 9:10 PM
Points: 7,693, Visits: 13,833
opc.three (3/27/2013)
GilaMonster (3/27/2013)
opc.three (3/27/2013)
At 50% I would rebuild. If you're having trouble with log size look into partitioning your table and indexes so you can rebuild smaller subsets of your index, ie only the partitions that need it.

Or switch to bulk-logged recovery model if possible.

True. That will help keep log size down but could increase tran log backup sizes.

OK, maybe negligibly larger. I have not paid too much attention to the actual differences but know they are larger. With a ton of index rebuild activity I figured it would be noticeable but maybe not as much I figured.

There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1436525
Posted Thursday, March 28, 2013 10:34 AM


Group: General Forum Members
Last Login: Tuesday, January 27, 2015 11:08 AM
Points: 21, Visits: 190
Thanks but bulk logged wont work for us. Also, we are use log shipping to another datacenter.
Post #1436608
Posted Thursday, March 28, 2013 10:54 AM



Group: General Forum Members
Last Login: Today @ 3:03 PM
Points: 22,555, Visits: 35,863
EL_oh_EL (3/28/2013)
Thanks but bulk logged wont work for us. Also, we are use log shipping to another datacenter.

Mind if we ask why it wouldn't work?

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1436614
Posted Friday, March 29, 2013 7:37 AM

SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 6:30 PM
Points: 4,907, Visits: 7,182
EL_oh_EL (3/27/2013)
Thanks! what i am trying to accomplish is to update the stats since they are not being kept up. I have thought about rebuilding the indexes since some are pretty fragmented >50%. but one concern is that our tables are huge like over 10Million rows of data so transaction log growth can grow pretty crazy. Is it rebuilding an indexes recommended based on how fragmented it is? Our trans log backups are done every 15 mins.

1) It is funny what people think is "huge" these days. I have a 131M row table on my laptop I use for data warehousing and column store index demos.

2) You cannot be successful managing a 1TB+ database on any RDBMS system without doing quite a few things right. Index mx and statistics updates are two of those things. The proper solution on HOW to manage those things best for YOUR SYSTEM cannot be determined without a lot more knowledge about your apps, data access/processing, mx window(s), SLAs, etc, etc. I could tell you things that would be general best practices that could totally fubar things for your system. I recommend you get a professional to help you determine what your needs really are and get things set up and mentor you on how to monitor/react to your systems needs.

3) Large tlogs are part and parcel of managing a large database. Plan for it or suffer the consequences.

4) Given log shipping to another datacenter you mentioned, are you compressing before shipping (assuming you have bandwidth/latency issues that usually come with that scenario)?


Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1436922
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse