I am running Ola Hallengren's SQL Maintenance scripts using the following command:
EXECUTE [dbo].[IndexOptimize] @Databases = 'MyDatabase' , @FragmentationLow = NULL , @FragmentationMedium = 'INDEX_REBUILD_OFFLINE' , @FragmentationHigh = 'INDEX_REBUILD_OFFLINE' , @FragmentationLevel1 = 10 , @FragmentationLevel2 = 30 , @UpdateStatistics = 'ALL' , @OnlyModifiedStatistics = 'Y' , @LogToTable = N'Y' , @TimeLimit = 23400 , @MinNumberOfPages = 1000 , @Indexes = 'ALL_INDEXES' , @MaxDOP = 7 , @SortInTempdb = 'Y'
Up until recently a number of the indices were unable to rebuild due to space constraints so I shifted tempDB to its own drive, configured tempDB to use 8 different files, and started sorting in tempDB (each tempDB file is roughly 10GB and growth set to 500MB each). Some indexes that were difficult to rebuild previously were able to complete relatively quickly, however, i have one index that I have been running for more than an hour in
MyDatabase and that database is rapidly increasing in size. Nothing else is currently running and TempDB has not increased in size at all.
Can anyone help me figure out why
MyDatabase is increasing so rapidly? Does anyone have any suggestions about what it could be causing this?
Running SQL Server 2012 if that helps. Thanks