Fulltext Index Study8:Resouce Consumption

一,查看Disk Consumption

1,通过SSMS查看Full-Text Index 的 Disk Consumption

在Storage-》Full Text Catalogs,选择某一个Catalog,点击属性,查看Catalog Size,就是位于Catalog中的属于fulltext的internal tables的总大小。

2,Population Schedule

通过Population Schedule tab,创建schedule和Job,按照schedule对fulltext index进行reorganize。

ALTER FULLTEXT CATALOG [fulltext_catalog_name]
REORGANIZE;

3,查询每个Table的Fragments的size

--fragment
SELECT
   [table] = OBJECT_SCHEMA_NAME(table_id) + ‘.‘ + OBJECT_NAME(table_id),
   logical_size_MB = CONVERT(DECIMAL(12,2), SUM(data_size/1024.0/1024))
FROM sys.fulltext_index_fragments
-- WHERE table_id = OBJECT_ID(‘dbo.specific_table_name‘)
GROUP BY table_id;

data_size:Logical size of the fragment in bytes.

二,在Fulltext Index Population时,查看memory consumption

参考《Fulltext Index Study6:Monitor Population

通过sys.dm_fts_memory_buffers 查看memory buffers used by a full-text crawl,通过sys.dm_fts_memory_pools查看memory pools used by a full-text crawl.

--returns the total shared memory owned by the Microsoft Full-Text Gatherer component
SELECT SUM(buffer_size * buffer_count)/1024 AS total_memory_KB
FROM sys.dm_fts_memory_pools

参考doc:

sys.fulltext_index_fragments (Transact-SQL)

sys.dm_fts_memory_pools (Transact-SQL)

sys.dm_fts_memory_buffers (Transact-SQL)

时间: 2024-08-06 03:20:25

Fulltext Index Study8:Resouce Consumption的相关文章

Fulltext Index Study3:Query

在query 语句中,可以使用 contains predicate来调用Fulltext Index,实现比like速度更快的查询.使用contains能够进行term的extract匹配查询或term的前缀匹配查询,还能够进行基于词根的steming查询,基于自定义同义词文件的synonym查询,基于距离和顺序的相邻term查询.和like 相比,contains不能进行后缀匹配查询.如果Fulltext Index 能够满足业务需求,那么Fulltext Index是一个非常不错的选择,跟

Fulltext Index Study4:management and performance

Only one full-text index is allowed per table. For a full-text index to be created on a table, the table must have a single, unique nonnull column. You can build a full-text index on columns of type char, varchar, nchar, nvarchar, text, ntext, image,

Fulltext Index Study2:Pupulate

Creating and maintaining a full-text index involves populating the index by using a process called a population (also known as a crawl). 由于创建Fulltext Index 会消耗大量的系统资源,因此Fulltext Index 必须在系统空间的时间进行maintain和crawl.在创建Fulltext Index时,通过指定 CHANGE_TRACKING

Fulltext Index Study1:Usage

一,在创建Fulltext Index的table上,必须使用Key Index(unique, single-key, non-nullable column) CREATE UNIQUE INDEX ui_dbLogID ON [dbo].[DatabaseLog]([DatabaseLogID]); The KEY INDEX must be a unique, single-key, non-nullable column. Select the smallest unique key

Fulltext Index Study6:Population monitor

一, filter daemon host sys.dm_fts_fdhosts Returns information on the current activity of the filter daemon host or hosts on the server instance. fdhost_process_id:Windows process ID of the filter daemon host. max_thread:Maximum number of threads in th

FULLTEXT INDEX全文索引

给现有的wxinfo表的sourceUrl 字段创建全文索引 ALTER TABLE wxinfoADD FULLTEXT INDEX sourceUrl (sourceUrl) 创建全文索引前: SELECT * FROM wxinfo WHERE sourceUrl LIKE '%查询字符串%' 创建全文索引后: SELECT * FROM wxinfo WHERE MATCH(sourceUrl) AGAINST('查询字符串') 备注1:目前,使用MySQL自带的全文索引时,如果查询字符

Fulltext Index Study7: maintain fragment

A fulltext index uses internal tables called full-text index fragments to store the inverted index data. 一,查看fragment 1, sys.fulltext_index_fragments Status of the fragment, one of: 0 = Newly created and not yet used 1 = Being used for insert during

在MYSQL中运用全文索引(FULLTEXT index)

在MYSQL中使用全文索引(FULLTEXT index) MYSQL的一个很有用的特性是使用全文索引(FULLTEXT index)查找文本的能力.目前只有使用MyISAM类型表的时候有效(MyISAM是默认的表类型,如果你不知道使用的是什么类型的表,那很可能就是 MyISAM).全文索引可以建立在TEXT,CHAR或者VARCHAR类型的字段,或者字段组合上.我们将建立一个简单的表用来解释各种特性.简单用法(MATCH()函数)对3.23.23以后的版本有效,复杂的用法(IN BOOLEAN

无语的index hint:手工分配哈希区,5小时不出结果,优化后20分钟

同事发来一个语句,说5个小时不出结果,我滴个神呀,想看看到底是什么垃圾语句造成的.于是叫同事发过来.不看不知道,一看吓一跳,3个表关联,强制使用了2个index hint,其中一个表9g,一个表67g,还有一个小表40Mb.无知的开发人员,以为走index就是快的,哎... 下面是同事发来的语句: select /*+ parallel(t,4) index(a,IDX_COMMBASUBSHIST_1) index(b,IDX_COMMCMSERVHIST_1)*/ 1, t.DISC_ID,