SQL Server 导入和导出向导错误
我正在尝试将 82k+ 行表从访问数据库导入到 SQL Server 2008。
使用 SQL Server 导入和导出向导，我在输入大约 78k 记录时收到错误。
错误如下：
Error 0xc0208265: Data Flow Task 1:
Failed to retrieve long data for column "members_notes".
Error 0xc020901c: Data Flow Task 1:
There was an error with output column "members_notes" (41) on output "OLE DB Source Output" (11).
The column status returned was: "DBSTATUS_UNAVAILABLE".
Error 0xc0209029: Data Flow Task 1:
SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "output column "members_notes" (41)" failed because error code 0xC0209071 occurred, and the error row disposition on "output column "members_notes" (41)" specifies failure on error.
Error 0xc0047038: Data Flow Task 1:
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.
The PrimeOutput method on component "Source - Query" (1) returned error code 0xC0209029.
The component returned a failure code when the pipeline engine called PrimeOutput().
The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
There may be error messages posted before this with more information about the failure.
access 数据库中的members_notes 列是一个备注字段。在该数据传输到的 SQL Server 表中，我已将该字段定义为 nvarchar(MAX)。
我搜索了此错误消息，发现文章建议缩小我的 SQL 数据库并清除执行导出/导入的计算机上的临时文件，但这些文章都不起作用。
还有其他人遇到过这个问题吗？
I'm trying to import an 82k+ row table from an access db to SQL Server 2008.
Using the SQL Server Import and Export Wizard, I get an error at about 78k records entered.
Here's the error:
Error 0xc0208265: Data Flow Task 1:
Failed to retrieve long data for column "members_notes".
Error 0xc020901c: Data Flow Task 1:
There was an error with output column "members_notes" (41) on output "OLE DB Source Output" (11).
The column status returned was: "DBSTATUS_UNAVAILABLE".
Error 0xc0209029: Data Flow Task 1:
SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
The "output column "members_notes" (41)" failed because error code 0xC0209071 occurred, and the error row disposition on "output column "members_notes" (41)" specifies failure on error.
Error 0xc0047038: Data Flow Task 1:
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.
The PrimeOutput method on component "Source - Query" (1) returned error code 0xC0209029.
The component returned a failure code when the pipeline engine called PrimeOutput().
The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
There may be error messages posted before this with more information about the failure.
The members_notes column in the access database is a memo field. In the SQL Server table to which this data is being transfered, I've defined the field as nvarchar(MAX).
I have searched for this error message and found articles suggesting to shrink my SQL db and clear my temp files on the computer doing the Export/Import, none of which worked.
Has anyone else run into this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我开始在 Access 数据库中搜索备注字段。最后一行的备注字段中包含“#Error”。当我单击该字段时，我收到以下消息：
压缩”和“修复”。这在该特定记录的备注字段中放置了一堆 # 字符。
然后我再次尝试了 SQL Server 导入和导出向导。它运行得很好，时间！
I started searching the memo field in the Access database. The last row contained '#Error' in the memo field. When I clicked in that field I got the following message:
I ran Compact and Repair on the Access database. That placed a bunch of # characters in the memo field for that specific record.
I then attempted the SQL Server Import and Export Wizard again. It worked perfectly that time!
我没有足够的声誉来提高你的答案 dpii 但它绝对对我有用。这个问题一直困扰着我，一个简单的压缩和修复就让它消失了。另请注意您上传时同时使用该文件的其他用户（或自己在 Access 中打开该文件），否则您可能会遇到此错误
I don't have enough reputation to up your answer dpii but it definitely worked for me. This problem was doing my head in and a simple compact and repair made it go away. Also beware other usesr using the file concurrently wyhile you are uploading (or having the file open yourself in Access) or you may encounter this error
这似乎是 SQL Server 2005 中的一个错误，应该修复，请参阅 此处
编辑：根据下面的评论，它已在 2008 SP1 CU5 中修复。
It seems this is a bug in SQL Server 2005 that supposed to be fixed, see here
Edit: Per your comment below, it is fixed in 2008 SP1 CU5.