SubSonic - 生成 SQL 使用 nvarchar 而不是 varchar,这会导致索引扫描而不是查找
我正在为我的应用程序使用 SubSonic SimpleRepository 模板。我在 VS2010 中创建了一个指向 SQL 2000 数据库的 ASP .NET WebForms 项目。
我遇到一个问题,SubSonic 在参数化查询中始终使用 nvarchar 而不是 varchar。这会导致 SQL 执行索引扫描而不是索引查找。我从 Profiler 中获取了 SQL 并对其进行了更改,以使参数 varchar 就像表的字段一样,并且执行速度非常快(<1 秒与 8 秒相比)。
来自 Profiler 的 SubSonic 查询
exec sp_executesql N'SELECT [t0].[ADDRESS_L1], [t0].[ADDRESS_L2], [t0].[ADDRESS_L3], [t0].[CITY], [t0].[COUNTRY] FROM [aveadmin].[SAPADD] AS t0 WHERE (([t0].[SITE_ID] = @p0) AND ((([t0].[ADDRESS_TYPE] = @p1) AND 1 <> 0) OR (([t0].[ADDRESS_TYPE] = @p2) AND 0 <> 0)))', N'@p0 nvarchar(16),@p1 nvarchar(2),@p2 nvarchar(2)', @p0 = N'BCF8A0A27E543EE1', @p1 = N'00', @p2 = N'03'
手动修改的查询
exec sp_executesql N'SELECT [t0].[ADDRESS_L1], [t0].[ADDRESS_L2], [t0].[ADDRESS_L3], [t0].[CITY], [t0].[COUNTRY] FROM [aveadmin].[SAPADD] AS t0 WHERE (([t0].[SITE_ID] = @p0) AND ((([t0].[ADDRESS_TYPE] = @p1) AND 1 <> 0) OR (([t0].[ADDRESS_TYPE] = @p2) AND 0 <> 0)))', N'@p0 varchar(16),@p1 varchar(2),@p2 varchar(2)', @p0 = N'BCF8A0A27E543EE1', @p1 = N'00', @p2 = N'03'
SITE_ID
和 ADDRESS_TYPE
是 varchars
。有没有办法强制查询使用 varchar
而不是 nvarchar
?
I am using the SubSonic SimpleRepository template for my application. I have created an ASP .NET WebForms project in VS2010 pointing to a SQL 2000 database.
I am having an issue where SubSonic is always using nvarchar in the parameterized queries instead of varchar. This causes SQL to do an Index Scan instead of an Index Seek. I have taken the SQL from the Profiler and altered it to make the parameters varchar like the table's fields and it executes very quickly (<1 second versus 8 seconds).
SubSonic Query from Profiler
exec sp_executesql N'SELECT [t0].[ADDRESS_L1], [t0].[ADDRESS_L2], [t0].[ADDRESS_L3], [t0].[CITY], [t0].[COUNTRY] FROM [aveadmin].[SAPADD] AS t0 WHERE (([t0].[SITE_ID] = @p0) AND ((([t0].[ADDRESS_TYPE] = @p1) AND 1 <> 0) OR (([t0].[ADDRESS_TYPE] = @p2) AND 0 <> 0)))', N'@p0 nvarchar(16),@p1 nvarchar(2),@p2 nvarchar(2)', @p0 = N'BCF8A0A27E543EE1', @p1 = N'00', @p2 = N'03'
Manually Modified Query
exec sp_executesql N'SELECT [t0].[ADDRESS_L1], [t0].[ADDRESS_L2], [t0].[ADDRESS_L3], [t0].[CITY], [t0].[COUNTRY] FROM [aveadmin].[SAPADD] AS t0 WHERE (([t0].[SITE_ID] = @p0) AND ((([t0].[ADDRESS_TYPE] = @p1) AND 1 <> 0) OR (([t0].[ADDRESS_TYPE] = @p2) AND 0 <> 0)))', N'@p0 varchar(16),@p1 varchar(2),@p2 varchar(2)', @p0 = N'BCF8A0A27E543EE1', @p1 = N'00', @p2 = N'03'
The SITE_ID
and ADDRESS_TYPE
are varchars
. Is there a way to force the query to use varchar
instead of nvarchar
?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
您必须修改 SubSonic 的源代码才能更改此行为。
You will have to modify the source code of SubSonic to change this behavior.
[先前的答案是正确的 - 更多详细信息如下。]
nvarchar 的使用被硬编码在 Sql2005Schema.cs 中名为 GetNativeType() 的函数中。修补和重建很容易。嘿,这是OSS!这就是源代码的用途!
这是代码。
理论上,生成的代码(请参阅 SQLServer.ttinclude)实际上确实生成 DbType.AnsiString 和 DbType.String 作为单独的类型。应该可以拆分 switch 语句并为其中一个生成“varchar”,为另一个生成“nvarchar”。也许作者认为这并不重要。我建议你尝试一下(但它可能会破坏单元测试)。
[Previous answer is correct -- further details follow.]
The use of nvarchar is hard-coded in a function called GetNativeType() in Sql2005Schema.cs. it's easy enough to patch and rebuild. Hey, this is OSS! This is what the source code is for!
Here is the code.
In theory, the generated code (see SQLServer.ttinclude) actually does generate DbType.AnsiString and DbType.String as separate types. It should be possible to split the switch statement and generate "varchar" for one and "nvarchar" for the other. Maybe the author thought it wouldn't matter. I suggest you give it a try (but it may break the unit tests).