首页 > 解决方案 > SQL Server 2016 查询 CPU 使用率过高

问题描述

每当我启动一个新的 SSMS 会话并执行该会话的第一个查询时,就会启动一个 Microsoft 查询。我在它执行时对其进行了跟踪,并确定它正在增加其中一个参数的值。有没有办法禁止它执行?

@_msparam_0=N'CO',@_msparam_1=N'JOHNP'
@_msparam_0=N'CO',@_msparam_1=N'JOHNP#'
@_msparam_0=N'CO',@_msparam_1=N'JOHNT'
@_msparam_0=N'CO',@_msparam_1=N'JOHNT#'
@_msparam_0=N'CO',@_msparam_1=N'JONG'
@_msparam_0=N'CO',@_msparam_1=N'JONG#'
@_msparam_0=N'CO',@_msparam_1=N'JONL'
@_msparam_0=N'CO',@_msparam_1=N'JONL#'
SELECT
u.name AS [Name],
u.principal_id AS [ID],
CAST(CASE WHEN u.principal_id < 5 OR u.principal_id = 16382 OR u.principal_id = 16383 THEN 1 ELSE 0 END AS bit) AS [IsSystemObject],
CASE WHEN N''U'' = u.type THEN 0 WHEN N''G'' = u.type THEN 1 WHEN N''S'' = u.type THEN 2 WHEN N''C'' = u.type THEN 3 WHEN N''K'' = u.type THEN 4 WHEN N''E'' = u.type THEN 5 WHEN N''X'' = u.type THEN 6 END AS [LoginType],
CAST(CASE dp.state WHEN N''G'' THEN 1 WHEN ''W'' THEN 1 ELSE 0 END AS bit) AS [HasDBAccess],
u.sid AS [Sid],
u.create_date AS [CreateDate],
u.modify_date AS [DateLastModified],
ISNULL(u.default_schema_name,N'''') AS [DefaultSchema],
ISNULL(ak.name,N'''') AS [AsymmetricKey],
ISNULL(cert.name,N'''') AS [Certificate],
ISNULL(suser_sname(u.sid),N'''') AS [Login],
ISNULL(u.default_language_lcid, -1) AS [DefaultLanguageLcid],
ISNULL(u.default_language_name,N'''') AS [DefaultLanguageName],
u.authentication_type AS [AuthenticationType],

        CASE
        WHEN N''C'' = u.type THEN 1
        WHEN N''K'' = u.type THEN 2        
        WHEN N''S'' = u.type AND SUSER_SNAME(u.sid) is null AND u.authentication_type != 2 THEN 3
        ELSE 0 END
       AS [UserType]
FROM
sys.database_principals AS u
LEFT OUTER JOIN sys.database_permissions AS dp ON dp.grantee_principal_id = u.principal_id and dp.type = @_msparam_0
LEFT OUTER JOIN sys.asymmetric_keys AS ak ON ak.sid = u.sid
LEFT OUTER JOIN sys.certificates AS cert ON cert.sid = u.sid
WHERE
(u.type in (''U'', ''S'', ''G'', ''C'', ''K'' ,''E'', ''X''))and(u.name=@_msparam_1)',N'@_msparam_0 nvarchar(4000),@_msparam_1 nvarchar(4000)

已确定这是 Intellisense 的问题。禁用 Intellisense 后,这不再是问题。我现在正试图弄清楚如何解决这个问题,以便我可以继续使用 Intellisense。

细节:

SSMS 版本:13.0.16106.4

对痕迹的进一步检查显示 Intellisense 是罪魁祸首

标签: sql-servertsql

解决方案


推荐阅读