0

我觉得我很慢,我有一个疑问:

SELECT K.RANK, physicalName, DocText, FileType
FROM Documents AS Docs
INNER JOIN CONTAINSTABLE(
    Documents,DocText, 'ISABOUT (pages Weight(0.7))'
) AS K
ON Docs.DocumentID = K.[KEY]
ORDER BY K.RANK;

它在 MSSQL 中工作,如果我这样做,中继器就会被填满:

SqlCommand objCommand = new SqlCommand("SELECT K.RANK, physicalName, DocText, FileType FROM Documents AS Docs INNER JOIN CONTAINSTABLE(Documents,DocText, 'ISABOUT ( pages Weight(0.7)                     )') AS K         ON Docs.DocumentID = K.[KEY]         ORDER BY K.RANK", objConn);

但是当我尝试用参数替换搜索文本时,它没有给我任何结果:

SqlCommand objCommand = new SqlCommand("SELECT K.RANK, physicalName, DocText, FileType FROM Documents AS Docs INNER JOIN CONTAINSTABLE(Documents,DocText, 'ISABOUT ( @SearchParams                         )') AS K         ON Docs.DocumentID = K.[KEY]         ORDER BY K.RANK", objConn);
        objCommand.Parameters.AddWithValue("@SearchParams", "pages Weight(0.7)");

我究竟做错了什么?

4

1 回答 1

2

整个搜索条件可以“参数化”:

SqlCommand objCommand = 
    new SqlCommand("SELECT K.RANK, physicalName, DocText, FileType FROM Documents AS Docs     
    INNER JOIN 
    CONTAINSTABLE(Documents,DocText, @SearchCondition) AS K 
    ON Docs.DocumentID = K.[KEY] ORDER BY K.RANK", objConn);

    objCommand.Parameters.AddWithValue("@SearchParams", "ISABOUT (pages Weight(0.7))");

编辑#1: AddWithValue应该避免,因为它会产生计划缓存污染。请阅读本文以更好地了解SQL Server 性能的这一方面。相反,我会使用Add方法(cmd.Parameters.Add)。

+

未正确指定参数长度时的查询性能和计划缓存问题

于 2013-09-30T18:43:34.003 回答