导出到平面文件时截断 BIDS 包错误

BIDS Package Error#39;s on Truncate while EXPORTING to flat file(导出到平面文件时截断 BIDS 包错误)
本文介绍了导出到平面文件时截断 BIDS 包错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

我有一个 BIDS 套餐.最后的数据流任务"将 SQL 表导出到平面文件.我在此过程中收到截断错误.导出到平面文件时什么会导致截断错误?错误发生在数据流任务"的数据流"选项卡下的OLE DB"元素中.

I have a BIDS package. The final "Data Flow Task" exports a SQL table to Flat File. I receive a truncation error on this process. What would cause a truncation error while exporting to flat file? The error was occurring within the "OLE DB" element under the Data Flow tab for the "Data Flow Task".

我已将该列设置为忽略截断错误并且导出工作正常.

I have set the column to ignore truncation errors and the export works fine.

我理解截断错误.我理解为什么将数据导入表时会发生这种情况.我不明白为什么在输出到平面文件时会发生这种情况.

I understand truncation errors. I understand why they would happen when you are importing data into a table. I do not understand why this would happen when outputting to a flat file.

推荐答案

发生这种情况的原因有很多.请确保下面列出的一些步骤:

This might be occurring for many reasons. Please make sure some of the steps listed below:

1) 检查必须与目标数据类型匹配的源数据类型.如果有不同,它可能会通过截断错误.

1) Check the source Data types that has to match with destination data type. If there are different it might through Truncation Error.

2) 检查是否有块 :- 您可以通过在目标之前创建数据查看器来检查这一点,并查看数据是否通过.

2) Check if there are blocks :- You can check this by creating Data viewer before the Destination and see the data come through.

这篇关于导出到平面文件时截断 BIDS 包错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

相关文档推荐

ibtmp1是非压缩的innodb临时表的独立表空间,通过innodb_temp_data_file_path参数指定文件的路径,文件名和大小,默认配置为ibtmp1:12M:autoextend,也就是说在文件系统磁盘足够的情况下,这个文件大小是可以无限增长的。 为了避免ibtmp1文件无止境的暴涨导致
SQL query to group by day(按天分组的 SQL 查询)
What does SQL clause quot;GROUP BY 1quot; mean?(SQL 子句“GROUP BY 1是什么意思?意思是?)
MySQL groupwise MAX() returns unexpected results(MySQL groupwise MAX() 返回意外结果)
MySQL SELECT most frequent by group(MySQL SELECT 按组最频繁)
Include missing months in Group By query(在 Group By 查询中包含缺失的月份)