简体   繁体   English

SSIS包作业失败,并出现VS_NEEDSNEWMETADATA错误

[英]SSIS package job fails with VS_NEEDSNEWMETADATA error

Hey I have SSIS project deployed in SQL Server SSIS. 嘿,我在SQL Server SSIS中部署了SSIS项目。 I also have a scheduled job which runs the deployed SSIS proeject from SQL Server. 我还有一个计划的作业,该作业从SQL Server运行已部署的SSIS项目。 (See the screenshot) Now when this job runs, (which is basically runnign the dtsx package) I get an error email which says that (请参见屏幕截图)现在,当此作业运行时(基本上是dtsx软件包运行的),我收到一条错误电子邮件,内容为

Load Fact Staging Table Failed on - Reporting Data Warehouse with following Error Messages: 加载事实暂存表失败-使用以下错误消息报告数据仓库:

"Fact Destination" failed validation and returned validation status "VS_NEEDSNEWMETADATA". “事实目的地”验证失败,并返回验证状态“ VS_NEEDSNEWMETADATA”。

I understand that this error can be solved if I open the dtsx package on the server using visual studio, I can fix it by right-click on the data source and then select edit, and then YEs. 我知道,如果我使用Visual Studio在服务器上打开dtsx包,则可以解决此错误,我可以通过右键单击数据源,然后选择“编辑”和“ YE”来修复它。 In my case since this only fails on production server, I do not have access to visual studio. 就我而言,由于这仅在生产服务器上失败,因此我无法访问Visual Studio。 So my question how can I fix this error by just using the dtsx package 所以我的问题是如何仅使用dtsx包来解决此错误

I am using SQL Server 2012 我正在使用SQL Server 2012 在此处输入图片说明

VS_NEEDSNEWMETADATA - this error means that underlying schema of tables that are involved in package was changed by someone, for instance column or table was renamed etc. VS_NEEDSNEWMETADATA-此错误意味着包中涉及的表的基础架构已由某人更改,例如,列或表已重命名等。

The dtsx package is XML file internally. dtsx软件包内部是XML文件。 If you are skillful enough you can adjust it in Notepad++ and resubmit a package. 如果您足够熟练,可以在Notepad ++中进行调整,然后重新提交软件包。

But I would still recommend to do it in BIDS/SSDT , since big change that you will end up with inconsistencies in your data flow lineages. 但是我仍然建议在BIDS / SSDT中进行此操作 ,因为发生巨大的变化最终会导致数据流谱系不一致。

Another workaround is to revert changes on database side that are the reason of such issue. 另一个解决方法是在数据库侧还原由于此问题而引起的更改。 Perhaps restore of backup side by side with further comparison of involved fact table 也许与所涉及事实表的进一步比较并排还原备份

If SSMS is available, you can relatively easy find some traces on where to search by using Schema Change History report: 如果SSMS可用,则可以使用“架构更改历史记录”报告相对容易地找到一些有关搜索位置的跟踪记录:

https://blog.sqlauthority.com/i/b/schema-change-history-1.jpg

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM