![]() She didn’t have automated index maintenance set up, but she periodically manually defragmented indexes that were more than 75% fragmented. The DBA explained that fragmentation wasn’t the problem. ![]() The DBA manager said, “Of course we’re handling fragmentation!” But a few queries were run and some large, seriously fragmented indexes were discovered in production. ![]() Early in the process they reviewed maintenance on the database server. There was no single smoking gun– there were 20 smoking guns!Ī team was formed of developers and IT staff to tackle the performance issue. Lots of code changes had been released recently, data was growing rapidly, and the hardware wasn’t the absolute freshest. Then things went badĪpplication performance plummeted. At the best of times, performance was dicey. ![]() Data was updated frequently throughout the day and index tuning was a serious challenge. Once up on a time, there was a database server with 500GB of data and a heavy read workload of dynamic queries. Index maintenance compacts a structure *and* changes physical order– both can be important!Įditors Note: this post was updated in June 2014 to link to an online index rebuild bug that can cause corruption. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |