We are following vendor recommendations for a index rebuild changing the fillfactor and enabling data compression, on the test server the results have us wondering what is going on that would cause the TLog to exceed 650 GB, (ran out of drive space). Why is the tlog growing so much?
SQL Server Version
Vendor code provided:
alter index all on dbo.ACC_LOG_DTL_IX rebuild with ( data_compression=PAGE, fillfactor=85, online=ON)
This is the script for the table and the one index.
CREATE TABLE [dbo].[ACC_LOG_DTL_IX]( [ACCESS_INSTANT] [numeric](16, 6) NOT NULL, [PROCESS_ID] [varchar](254) NOT NULL, [DATA_MNEMONIC_ID] [varchar](15) NOT NULL, [STRING_VALUE] [varchar](2000) NULL, [INTEGER_VALUE] [numeric](18, 0) NULL, CONSTRAINT [PK_ACC_LOG_DTL_IX] PRIMARY KEY CLUSTERED ( [ACCESS_INSTANT] ASC, [PROCESS_ID] ASC, [DATA_MNEMONIC_ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]