LOG IO峰值 [英] LOG IO spikes

问题描述

我们在LOG IO中看到很多峰值，并且它发生在具有ntext列的表上.这会有助于大部分日志活动吗?

We are seeing lot of spikes in LOG IO and it happens on a table with ntext column. COuld this be contributing to much of the log activity?

如果是这种情况，除了重新设计表格以外，还有其他选择吗?

If this is the case, other than redesigning the table are there any other options?

grajee

推荐答案

Grajee，

首先，让我提醒您，不建议使用ntext，以后可以将其删除，因此，为避免不得不在短时间内进行更改，我建议使用nvarchar或varchar.此处的更多信息:https://docs.microsoft.com/zh-cn/sql/t-sql/data-types/ntext-text-and-image-transact-sql?view=sql-server-2017

日志IO峰值将取决于对数据库执行的写操作的数量及其大小.如果对该表的写操作影响到"Value"，则该值不会被写入.字段，并且要处理的数据量很大，那么您可以获取这些 峰值，但是使用nvarchar或varchar时也会出现峰值，这取决于写入操作的数量和要处理的数据量.

Hi Grajee,

First of all let me alert you that ntext is deprecated and can be removed in the future, so to avoid having to make changes in a short time I suggest to use nvarchar or varchar. More information here: https://docs.microsoft.com/en-us/sql/t-sql/data-types/ntext-text-and-image-transact-sql?view=sql-server-2017

Log IO spikes will depend on the number of write operations being done on the database and the size of them. If the write operations on this table affect the "Value" field and the amount of data being handle is considerable then you can get those spikes but you will also get them when using nvarchar or varchar as it will depend on the number of write operations and the amount of data being handle.

这篇关于LOG IO峰值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！