• Jack Corbett (8/18/2014)


    As far as index sizes, there certainly are cases where an index can be nearly as large as the base table itself, and I'd argue that if that is the case that there is probably some kind of application or database design issue. Before I'd go that far I need to know if any index maintenance is being done on the database? Are you ever rebuilding or reorganizing the indexes to reduce fragmentation? Fragmentation can cause the size of an index to grow beyond what is really needed.

    You should look at potentially moving indexes onto a separate file group and possibly partitioning, but as this is a vendor database you'd need to work with them, especially for partitioning as changes like this could violate a support agreement.

    Since you are on a SAN (I'm no SAN expert), I'd think you could just expand LUN that is being presented to the server for the data drive and have space. My understanding is that this is one of the benefits of running on a SAN.

    This was a great idea. Instead of splitting the data file across 2 LUNs as per my original concept, we basically took 2 hard drives from the RAID 5 LUN and added it to the RAID 10 Data LUN and extended the drive from windows disk management thereby increasing the space by 135 GB. So, the issue is resolved for now. Thanks for the idea Jack.:-)