Oracle到SQL2005 DATETIME字段在SSIS中溢出 [英] Oracle to SQL2005 DATETIME field overflows in SSIS

问题描述

我正在使用SSIS将数据从Oracle导入SQL Server 2005。我认为Oracle中的datetime字段存储的精度高于SQL Server 2005DATETIME字段将允许，导致溢出错误。获取表格的最佳做法是什么？

这些表有很多datetime字段，有很多表，所以如果没有，每个领域都需要大量的手工工作...

我已经阅读了 http://stackoverflow.com/questions/2231028/dealing-with-timestamp-datetime -when-replication-data-from-oracle-to-sql-server-using ，这可以工作，但是我必须为每个字段，每个表都这样做，我宁愿拥有一个通用设置或过程...

任何想法？

解决方案

只是将其标记为已回复，因为似乎没有全局设置。

I'm importing data from Oracle to SQL Server 2005 using SSIS. I think the datetime fields in Oracle are stored to a higher precision than SQL Server 2005 "DATETIME" fields will allow, causing overflow errors. What's the best practice for getting the table in?

These tables have lots of datetime fields, and there are lots of tables, so it'd be awesome if there wasn't a ton of manual work for each field...

I've read http://stackoverflow.com/questions/2231028/dealing-with-timestamp-datetime-when-copying-data-from-oracle-to-sql-server-using and that could work, but I'd have to do that for each field, for every table, and I'd rather have a universal setting or process...

Any ideas?

解决方案

Just flagging this as 'answered' since there appears to be no global setting.

这篇关于Oracle到SQL2005 DATETIME字段在SSIS中溢出的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！