Project Server 2010年6月2012 CU关于报告数据库分配成本修复的问题 [英] Project Server 2010 June 2012 CU Question about the Reporting Database Assignment Cost Fix
问题描述
您好。我阅读了项目服务器2010年6月2012 CU下修复的问题，并希望了解有关此软件包中解决的其中一个修补程序的更多信息，因为这是我们现有客户关注的问题。
http://support.microsoft.com/kb/2598375
"此修补程序包修复的问题"列出并注意说明"在Project Server 2010的报表数据库中错误地计算时间分段剩余成本和实际成本"的行
有人可以向我提供有关此修复程序的更多详细信息吗？它是如何复制的，我们能否确定在我们的客户环境中是否遇到过这个问题？我们需要了解每个客户对此问题的重要性，以便我们建议
正确的前进路径。可以理解地安装CU可以消除风险，但对于我们的一些客户而言，这种类型的更新会启动一系列变更管理流程，因为环境通常与其他业务线应用程序共享。它甚至可以在生产到达生产之前花费几个月的时间，所以在开始可以被认为是组织的大型工作组合之前，我们的客户首先要了解这个问题是很重要的。与此同时，现在解释
SQL和OLAP报告会产生什么影响？它们中的数据可以信任吗？
关心，
Piet Remen
http://pietremen.blogspot.com.au
嗨Piet，
我自己没有介入过这个问题。但我认为您应该能够比较msp_epmassignmentbyday和msp_epmassignment的实际成本。如果
报告数据库中存在时间分段成本数据问题，它们通常应该是相同的。
问候
克里斯托弗
Hello. I read the issues fixed under the project server 2010 June 2012 CU and would like to find out more information about one of the fixes addressed in this package as it is a concern to our existing clients.
http://support.microsoft.com/kb/2598375
"Issues that this hotfix package fixes" list and note the line which states "Timephased remaining costs and actual costs are calculated incorrectly in the report database in Project Server 2010"
Can someone please provide me with more detail on this fix? How is it reproduced and can we identify if this issue is being experienced in our client environments? We need to understand the weight of this issue for each of our clients so we can recommend the correct path forward. Understandably installing the CU removes the risk but for some of our clients this type of update intiates a series of change management processes as the environment is often shared with other Line of business applications. It can take a few months even before this reaches production so it is important our clients understand the issue first before initiating what can be deemed to be a large comoponent of work for the organisation. In the mean time, what is the impact when interpreting SQL and OLAP reports for now? Can the data in them be trusted?
Regards,
Piet Remen
http://pietremen.blogspot.com.au
Hi Piet,
I have not stepped across the issue myself. But I think you should be able to compare the actual cost from msp_epmassignmentbyday and msp_epmassignment. They should normally be the same and would not if there is an issue with timephased cost data in the reporting database.
Regards
Christoph
这篇关于Project Server 2010年6月2012 CU关于报告数据库分配成本修复的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
