我的数据库在2.5TB左右。每天运行重建索引是一个好做法吗?
我们每天删除大约20 GB的数据&同时删除分区&我们将添加新的分区。运行重建索引需要8小时,有时是24小时。在此期间,日志文件将增加到300 GB。
我们需要向客户发送数据库碎片的每日报告。看到99 %或98%的人害怕。请建议一下。
表的大小是70 99&对于这个表碎片级别,每天将是99%。不知道是什么让客户要求每日报告的碎片化水平,但他只是每天需要它。
发布于 2016-09-30 10:38:36
首先,您应该考虑索引的page_count。如果page_count小于1000 (或您所决定的),那么您应该使用忽略索引。
我们有一个维护脚本,它分析索引的page_count和分段,并遵循以下指导方针:
ALTER INDEX … REORGANIZE)ALTER INDEX … REBUILD)(企业版本的ONLINE= ON)这是一个了解您目前所处位置的起点:-
SELECT dbtables.[name] AS 'Table'
,dbindexes.[name] AS 'Index'
,indexstats.avg_fragmentation_in_percent
,CASE
WHEN indexstats.avg_fragmentation_in_percent < 10
THEN 'NOTHING'
WHEN indexstats.avg_fragmentation_in_percent >= 10
AND indexstats.avg_fragmentation_in_percent < 30
THEN 'REORGANIZE'
WHEN indexstats.avg_fragmentation_in_percent >= 30
THEN 'REBUILD'
END
,indexstats.page_count
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, NULL) AS indexstats
INNER JOIN sys.tables dbtables ON dbtables.[object_id] = indexstats.[object_id]
INNER JOIN sys.schemas dbschemas ON dbtables.[schema_id] = dbschemas.[schema_id]
INNER JOIN sys.indexes AS dbindexes ON dbindexes.[object_id] = indexstats.[object_id]
AND indexstats.index_id = dbindexes.index_id
WHERE indexstats.database_id = DB_ID()
AND page_count > 1000
AND dbindexes.NAME IS NOT NULL
ORDER BY indexstats.avg_fragmentation_in_percent DESC这完全取决于你的要求。当您每周只重建一次时,性能是如何影响的?你能在重建后每周直接发送一次报告吗?我将在测试环境中(如果可能的话)将性能作为基线,如果性能不降低太多,则每周只执行一次索引维护。
一份经纪人的工作可以是:-
DECLARE @Indexes AS TABLE (
ID INT IDENTITY(1, 1) NOT NULL
,TableNm VARCHAR(500) NOT NULL
,IndexNm VARCHAR(500) NOT NULL
,FragPerc DECIMAL(16, 3) NOT NULL
,RecAction VARCHAR(50) NOT NULL
,PageCount INT NOT NULL
)
INSERT INTO @Indexes
SELECT dbtables.[name] AS 'Table'
,dbindexes.[name] AS 'Index'
,indexstats.avg_fragmentation_in_percent
,CASE
WHEN indexstats.avg_fragmentation_in_percent < 10 --change all levels to your requirement
THEN 'NOTHING'
WHEN indexstats.avg_fragmentation_in_percent >= 10
AND indexstats.avg_fragmentation_in_percent < 30
THEN 'REORGANIZE'
WHEN indexstats.avg_fragmentation_in_percent >= 30
THEN 'REBUILD'
END
,indexstats.page_count
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, NULL) AS indexstats
INNER JOIN sys.tables dbtables ON dbtables.[object_id] = indexstats.[object_id]
INNER JOIN sys.schemas dbschemas ON dbtables.[schema_id] = dbschemas.[schema_id]
INNER JOIN sys.indexes AS dbindexes ON dbindexes.[object_id] = indexstats.[object_id]
AND indexstats.index_id = dbindexes.index_id
WHERE indexstats.database_id = DB_ID()
AND page_count > 1000
AND dbindexes.NAME IS NOT NULL
ORDER BY indexstats.avg_fragmentation_in_percent DESC
DELETE FROM @Indexes WHERE RecAction = 'NOTHING'
DECLARE @sql AS VARCHAR(MAX)
DECLARE @whilecount AS INT = 1
DECLARE @rowcount AS INT = (
SELECT MAX(ID)
FROM @Indexes
)
DECLARE @IndexNm AS VARCHAR(500)
DECLARE @TableNm AS VARCHAR(500)
DECLARE @RecAction AS VARCHAR(50)
WHILE @whilecount <= @rowcount
BEGIN
SET @IndexNm = (
SELECT IndexNm
FROM @Indexes
WHERE ID = @whilecount
)
SET @TableNm = (
SELECT TableNm
FROM @Indexes
WHERE ID = @whilecount
)
SET @RecAction = (
SELECT RecAction
FROM @Indexes
WHERE ID = @whilecount
)
IF @RecAction = 'REBUILD'
BEGIN
SET @sql = 'ALTER INDEX [' + @IndexNm + '] ON [' + @TableNm + '] REBUILD WITH (FILLFACTOR = 98, ONLINE = ON);' --change depending on SQL version
END
ELSE IF @RecAction = 'REORGANIZE'
BEGIN
SET @sql = 'ALTER INDEX [' + @IndexNm + '] ON [' + @TableNm + '] REORGANIZE;'
END
EXECUTE (@sql);
SET @whilecount += 1
END https://dba.stackexchange.com/questions/151084
复制相似问题