Sql Server 索引使用情況及優(yōu)化的相關(guān)Sql語(yǔ)句分享
更新時(shí)間:2012年05月27日 22:59:29 作者:
Sql Server 索引使用情況及優(yōu)化的相關(guān) Sql 語(yǔ)句,非常好的SQL語(yǔ)句,記錄于此,需要的朋友可以參考下
復(fù)制代碼 代碼如下:
--Begin Index(索引) 分析優(yōu)化的相關(guān) Sql
-- 返回當(dāng)前數(shù)據(jù)庫(kù)所有碎片率大于25%的索引
-- 運(yùn)行本語(yǔ)句會(huì)掃描很多數(shù)據(jù)頁(yè)面
-- 避免在系統(tǒng)負(fù)載比較高時(shí)運(yùn)行
-- 避免在系統(tǒng)負(fù)載比較高時(shí)運(yùn)行
declare @dbid int
select @dbid = db_id()
SELECT o.name as tablename,s.* FROM sys.dm_db_index_physical_stats (@dbid, NULL, NULL, NULL, NULL) s,sys.objects o
where avg_fragmentation_in_percent>25 and o.object_id =s.object_id
order by avg_fragmentation_in_percent desc
GO
-- 當(dāng)前數(shù)據(jù)庫(kù)可能缺少的索引
-- 非常好用的 Sql 語(yǔ)句
select d.*
, s.avg_total_user_cost
, s.avg_user_impact
, s.last_user_seek
,s.unique_compiles
from sys.dm_db_missing_index_group_stats s
,sys.dm_db_missing_index_groups g
,sys.dm_db_missing_index_details d
where s.group_handle = g.index_group_handle
and d.index_handle = g.index_handle
order by s.avg_user_impact desc
go
-- 自動(dòng)重建或重新組織索引
-- 比較好用,慎用,特別是對(duì)于在線 DB
-- Ensure a USE <databasename> statement has been executed first.
SET NOCOUNT ON;
DECLARE @objectid int;
DECLARE @indexid int;
DECLARE @partitioncount bigint;
DECLARE @schemaname nvarchar(130);
DECLARE @objectname nvarchar(130);
DECLARE @indexname nvarchar(130);
DECLARE @partitionnum bigint;
DECLARE @partitions bigint;
DECLARE @frag float;
DECLARE @command nvarchar(4000);
-- Conditionally select tables and indexes from the sys.dm_db_index_physical_stats function
-- and convert object and index IDs to names.
SELECT
object_id AS objectid,
index_id AS indexid,
partition_number AS partitionnum,
avg_fragmentation_in_percent AS frag
INTO #work_to_do
FROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL , NULL, 'LIMITED')
WHERE avg_fragmentation_in_percent > 10.0 AND index_id > 0;
-- Declare the cursor for the list of partitions to be processed.
DECLARE partitions CURSOR FOR SELECT * FROM #work_to_do;
-- Open the cursor.
OPEN partitions;
-- Loop through the partitions.
WHILE (1=1)
BEGIN;
FETCH NEXT
FROM partitions
INTO @objectid, @indexid, @partitionnum, @frag;
IF @@FETCH_STATUS < 0 BREAK;
SELECT @objectname = QUOTENAME(o.name), @schemaname = QUOTENAME(s.name)
FROM sys.objects AS o
JOIN sys.schemas as s ON s.schema_id = o.schema_id
WHERE o.object_id = @objectid;
SELECT @indexname = QUOTENAME(name)
FROM sys.indexes
WHERE object_id = @objectid AND index_id = @indexid;
SELECT @partitioncount = count (*)
FROM sys.partitions
WHERE object_id = @objectid AND index_id = @indexid;
-- 30 is an arbitrary decision point at which to switch between reorganizing and rebuilding.
IF @frag < 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE';
IF @frag >= 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD';
IF @partitioncount > 1
SET @command = @command + N' PARTITION=' + CAST(@partitionnum AS nvarchar(10));
EXEC (@command);
PRINT N'Executed: ' + @command;
END;
-- Close and deallocate the cursor.
CLOSE partitions;
DEALLOCATE partitions;
-- Drop the temporary table.
DROP TABLE #work_to_do;
GO
-- 查看當(dāng)前數(shù)據(jù)庫(kù)索引的使用率
-- 非常的有用
SELECT
object_name(object_id) as table_name,
(
select name
from sys.indexes
where object_id = stats.object_id and index_id = stats.index_id
) as index_name,
*
FROM sys.dm_db_index_usage_stats as stats
WHERE database_id = DB_ID()
order by table_name
-- 指定表的索引使用情況
declare @table as nvarchar(100)
set @table = 't_name';
SELECT
(
select name
from sys.indexes
where object_id = stats.object_id and index_id = stats.index_id
) as index_name,
*
FROM sys.dm_db_index_usage_stats as stats
where object_id = object_id(@table)
order by user_seeks, user_scans, user_lookups asc
--End Index 分析優(yōu)化的相關(guān) Sql
您可能感興趣的文章:
- 數(shù)據(jù)庫(kù)SQL語(yǔ)句優(yōu)化總結(jié)(收藏)
- SQL語(yǔ)句性能優(yōu)化(續(xù))
- 如何優(yōu)化SQL語(yǔ)句(全)
- sql語(yǔ)句優(yōu)化之SQL Server(詳細(xì)整理)
- SQL Server中的SQL語(yǔ)句優(yōu)化與效率問(wèn)題
- MySQL SQL語(yǔ)句優(yōu)化的10條建議
- 如何優(yōu)化SQL語(yǔ)句的心得淺談
- 淺談MySQL中優(yōu)化sql語(yǔ)句查詢(xún)常用的30種方法
- SQL語(yǔ)句優(yōu)化方法30例(推薦)
- SQLServer 優(yōu)化SQL語(yǔ)句 in 和not in的替代方案
- oracle下一條SQL語(yǔ)句的優(yōu)化過(guò)程(比較詳細(xì))
- SQL SERVER 的SQL語(yǔ)句優(yōu)化方式小結(jié)
- 常用SQL語(yǔ)句優(yōu)化技巧總結(jié)【經(jīng)典】
相關(guān)文章
數(shù)據(jù)庫(kù)中聚簇索引與非聚簇索引的區(qū)別[圖文]
在《數(shù)據(jù)庫(kù)原理》里面,對(duì)聚簇索引的解釋是:聚簇索引的順序就是數(shù)據(jù)的物理存儲(chǔ)順序,而對(duì)非聚簇索引的解釋是:索引順序與數(shù)據(jù)物理排列順序無(wú)關(guān)。正式因?yàn)槿绱耍砸粋€(gè)表最多只能有一個(gè)聚簇索引2012-02-02
數(shù)據(jù)庫(kù)分頁(yè)存儲(chǔ)過(guò)程代碼
數(shù)據(jù)庫(kù)分頁(yè)存儲(chǔ)過(guò)程代碼...2007-04-04
SQL Server高級(jí)內(nèi)容之子查詢(xún)和表鏈接概述及使用
子查詢(xún)就是在查詢(xún)的where子句中的判斷依據(jù)是另一個(gè)查詢(xún)的結(jié)果,表鏈接就是將多個(gè)表合成為一個(gè)表,但是不是向union一樣做結(jié)果集的合并操作,但是表鏈接可以將不同的表合并,并且共享字段,感興趣的你可以了解下本文2013-03-03
SQL Server數(shù)據(jù)庫(kù)安裝時(shí)常見(jiàn)問(wèn)題解決方案集錦
對(duì)于初學(xué)者來(lái)說(shuō),安裝SQL Server數(shù)據(jù)庫(kù)時(shí),常常會(huì)有一些問(wèn)題的出現(xiàn),這篇文章就是針對(duì)安裝時(shí)常見(jiàn)問(wèn)題總結(jié)的解決方案,需要的朋友可以參考下2015-08-08
SQL Server Alert發(fā)送告警郵件少了的原因
這篇文章主要為大家詳細(xì)介紹了SQL Server Alert發(fā)送告警郵件少了的原因,具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2017-06-06
SQL Server數(shù)據(jù)庫(kù)自動(dòng)收縮配置指南
在數(shù)據(jù)庫(kù)管理中,隨著數(shù)據(jù)的增刪,數(shù)據(jù)庫(kù)文件的大小會(huì)不斷變化,導(dǎo)致空間浪費(fèi)和性能下降,SQL Server提供了自動(dòng)收縮功能,本文將深入探討如何在SQL Server中配置數(shù)據(jù)庫(kù)的自動(dòng)收縮,需要的朋友可以參考下2024-07-07
SQL查詢(xún)某列指定長(zhǎng)度的字符串多余的用省略號(hào)來(lái)表示
有時(shí)候?yàn)榱嗣烙^,只需要顯示前面幾個(gè)字符串,剩下的可以用省略號(hào)來(lái)表示,下面有個(gè)不錯(cuò)的示例,感興趣的朋友可以參考下2013-11-11
SQL Server中的執(zhí)行引擎入門(mén) 圖解
當(dāng)查詢(xún)優(yōu)化器(Query Optimizer)將T-SQL語(yǔ)句解析后并從執(zhí)行計(jì)劃中選擇最低消耗的執(zhí)行計(jì)劃后,具體的執(zhí)行就會(huì)交由執(zhí)行引擎(Execution Engine)來(lái)進(jìn)行執(zhí)行2012-05-05

