March 5, 2013 at 6:36 am
First of all there are no performance problems at the moment.
Study of the three tables with the larges number of rows.
A 51636579 rows. Avg. Page Density 60.20 %
Scan Density 14.57% [183983:1262392]
B 51636579 rows. Avg. Page Density 68.96
Scan Density 14.73% [151056:1025730]
C 46238580 rows. Avg. Page Density 57.37%
Scan Density 13.33% [34965:262306]
A rebuild (90 percent) on these three tables, would result in
1. Faster database.
2. 10 Gigabyte of storage less needed.
3. Cache will be used more effectively.
4. Backups become smaller. (Compressed backups ?)
5. Backups become faster.
Database: Microsoft SQL Server Standard Edition (64-bit)
Version: 9.00.3042.00
Server Startup Time: Jul 20 2011 8:25 AM
TotalSpaceUsesage: 41.631,56 Mb
So I think an online backup is not possible.
As said there are no performance problems. But the advantages of using the resources more effectively might be interesting. So what advise would you give about the Rebuild? There is no real OFFLINE maintenance window.
Ben Brugman
March 5, 2013 at 6:38 am
Rebuild if you can, reorganise if you can't.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 5, 2013 at 8:15 am
I believe online rebuild is not an available in Standard Edition.
Without a maintenance window or Enterprise Edition, rebuilding isn't going be an option for you.
So you're left with reorganizing.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply