PeopleSoft 安装是否需要持续的日常数据库脚本来解决“问题”？
我对 PeopleSoft 的经验很少，但已经能够支持安装。这个问题可能跨越服务器故障，但肯定是面向开发人员的。
每天，我们都有一位 PeopleSoft“开发人员”编写脚本来修复记录/日记条目/批准状态等。对我来说，这简直就是“错误的安装”和拙劣的自定义。这是正常的吗？让员工必须每天编写脚本才能保持工作正常运行是最佳实践吗？
注：这里不存在欺诈行为，他这样做时得到了会计部门的完全批准。
I have very little PeopleSoft experience but have been put in a position to support an install. This question could straddles serverfault but is certainly developer oriented.
On a daily basis, we have a PeopleSoft "developer" who writes scripts to fix records/journal entries/approval status etc. To me this screams "bad install" and botched customizations. Is this normal? Is it best practice to have an employee having to write scripts daily just to keep things running?
Note: there is no fraud happening here, he has the full approval of the accounting department when doing this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不太可能是安装的问题。可能的原因：
如果您只有一名管理员，并且只有一名开发人员，那么当我听说定制代码存在很多问题时，我会感到震惊。
回到问题：需要定期进行 SQL 更新来修复数据是不正常的。是的，这种情况会发生，但不会太频繁。最终用户也有可能可以从应用程序中修复它，但由于某种原因而没有这样做。
It is unlikely that it is the installation. Likely causes:
If you only have one admin, though, and you have only one developer, I would be shocked to hear that there is much in the way of custom code.
Back to the question: It is not normal to need to do SQL updates regularly to fix data. Yes, it happens, but not too often. It is also possible that the end users could fix it from the application, but do not for some reason.
即席 SQL 更新可能很危险，并且 SQL 可能会根据每个请求而更改。由于临时脚本通常需要周转，因此很难对其进行全面测试。
我认为这些“修复”实际上是在进行系统未实现的更改。
更明智的做法是：
请注意您的下一次升级：应用程序表在最近的版本中发生了很多变化。
Ad-hoc SQL updates can be dangerous and the SQL may change on every request. It is difficult to fully test ad-hoc scripts due to the turnaround they typically require.
I assume these "fixes" are in fact making changes not implemented by the system.
It would be more sensible to either:
Watch out on your next upgrade: application tables have had a lot of changes in recent releases.