它适用于大多数查询,但我不时会得到一些非常奇怪的超时.最奇怪的是,只有在通过dapper执行sql时才会发生此超时.如果我从分析器中复制执行的查询并在Management Studio中运行它的速度很快并且工作正常.而且这不仅仅是暂时的问题.查询始终通过dapper超时,并在Management Studio中始终正常工作.

exec sp_executesql N'SELECT Item.Name,dbo.PlatformTextAndUrlName(Item.ItemId) As PlatformString,dbo.MetaString(Item.ItemId) As MetaTagString,Item.StartPageRank,Item.ItemRecentViewCount
                    NAME_SRCH.RANK as NameRank,DESC_SRCH.RANK As DescRank,ALIAS_SRCH.RANK as AliasRank,Item.itemrecentviewcount,(COALESCE(ALIAS_SRCH.RANK,0)) + (COALESCE(NAME_SRCH.RANK,0)) + (COALESCE(DESC_SRCH.RANK,0) / 20) + Item.itemrecentviewcount / 4 + ((CASE WHEN altrank > 60 THEN 60 ELSE altrank END) * 4) As SuperRank
                    FROM dbo.Item
                    INNER JOIN dbo.License on Item.LicenseId = License.LicenseId

                    LEFT JOIN dbo.Icon on Item.ItemId = Icon.ItemId
                    LEFT OUTER JOIN FREETEXTTABLE(dbo.Item,name,@SearchString) NAME_SRCH ON
                    Item.ItemId = NAME_SRCH.[KEY] 
                    LEFT OUTER JOIN FREETEXTTABLE(dbo.Item,namealiases,@SearchString) ALIAS_SRCH ON
                    Item.ItemId = ALIAS_SRCH.[KEY] 
                    INNER JOIN FREETEXTTABLE(dbo.Item,*,@SearchString) DESC_SRCH ON
                    Item.ItemId = DESC_SRCH.[KEY]
                    ORDER BY SuperRank DESC OFFSET @Skip ROWS FETCH NEXT @Count ROWS ONLY',N'@Count int,@SearchString nvarchar(4000),@Skip int',@Count=12,@SearchString=N'Box,com',@Skip=0

这是我从sql事件探查器复制粘贴的查询.我在我的代码中执行它.

using (var connection = new sqlConnection(ConfigurationManager.ConnectionStrings["Conn"].ToString())) {
            connection.Open();
            var items = connection.Query<MainItemForList>(query,new { SearchString = searchString,PlatformId = platformId,_LicenseFilter = licenseFilter,Skip = skip,Count = count },buffered: false);
            return items.ToList();
        }

我不知道从哪里开始.我想必须有一些与dapper一起发生的事情,因为当我执行代码时它工作正常.

正如您在此屏幕截图中看到的那样.这是先通过代码执行,然后通过Management Studio执行的相同查询.

我还可以补充说,这只是(我认为)当我有两个或更多的单词或我在搜索字符串中有一个“停止”字符时发生.所以它可能与全文搜索有关,但我无法弄清楚如何调试它,因为它完美地从Management Studio.

更糟糕的是,它在我的localhost上工作正常,几乎相同的数据库来自代码和Management Studio.