There's a storm brewing, or maybe I should say firestorm. A customer has recently implemented SQL Server 2012 Always On but that's not the most important bit.
A list of fires to be put out has been arrived at, and one of them is "incorrect fill factor". Someone in their infinite wisdom had decided to recreate a multi-billion-record table with over 10 indexes without specifying the FILLFACTOR for the indexes during the recreation (showing in sys.indexes as 0%).
I have always though that page splitting is bad, but in real terms, how bad is
bad? Is it worse than not having the index at all? Is there a concrete argument for putting out this fire before the others? Note: it will take a significant amount of time for each index rebuild.
FYI - SQL Server 2012 Enterprise Edition