varchar(max)数据类型odbc映射到ms

本文介绍了varchar(max)数据类型odbc映射到ms-access2003的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我已经在SQL Server 2005上使用我们的遗留应用程序测试了在相反的文本中定义varchar(max)的区别.一切进展顺利，在特定的测试案例中，新的数据类型将读取次数从78减少到了8代表我们不想错过的性能提升.

i have tested the difference between defining varchar(max) in opposite text with our legacy application on a SQL Server 2005. All went very well and the new datatype reduced in a particular test case the amount of reads from 78 to 8 that represents a performance gain which we dont want to miss.

但是现在在版本2008的目标sqlserver上我遇到了一个问题:数据类型varchar(max)的列现在已映射到 msaccess2003 数据类型的text(255).

But now on the target sqlserver of version 2008 i get a problem: the columns of datatype varchar(max) are now mapped to the msaccess2003 datatype text(255).

此odbc映射在哪里定义?必须更改哪个参数才能将所需的varchar(max)映射到备忘录?

Where is this odbc mapping defined? Which parameter must be changed to get the desired mapping varchar(max) to memo?

和平

冰

更新:

现在我知道，当我远程登录Win 2008/SQL Server 2008时连接Access ODBC-Sources时，varchar(max)到ms-access-datatype备忘录的映射是正确的. 我们在局域网中工作，当登录Win2003-Citrix-Server并使用ms-access连接ODBC-Sources时，映射出错. 情况很奇怪，怎么回事?

Now i know that when i connect the Access ODBC-Sources while remotely logged on the Win 2008 / SQL Server 2008 the mapping of varchar(max) to ms-access-datatype memo is correct. We work in a LAN and while logged on the Win2003-Citrix-Server connecting the ODBC-Sources with ms-access the mapping goes wrong. Very weird situation, whats is going on?

推荐答案

尽管本文涉及导入，但您可能会对它感兴趣: www.windows-tech.info/15/313c8cc3ac​​03f313.php

While this article refers to importing, it may be of interest to you: www.windows-tech.info/15/313c8cc3ac03f313.php

它指出:

您在SQL Server中的字段应为 NVARCHAR(MAX)直接映射到 Access中的MEMO字段.数据类型 在该字段的SSIS包中 应该是DT_NTEXT.

Your field in SQL Server should be an NVARCHAR(MAX) to map directly to the MEMO field in Access. The data types inside the SSIS package for that field should be DT_NTEXT.

-菲尔·布拉默(phil Brammer)

-- Phil Brammer