问题描述
我意识到我的问题有点概念性，但在继续我的项目之前我需要对它进行排序。
我在SQL中创建了几十个视图，其中一些非常复杂，涉及12个以上的表。我在商业报告excel文件中使用这些视图来做一些商业智能。
我现在正试图将该excel报告迁移到c＃中的成熟应用程序中使用wpf，mvvm模式和实体框架。
我相信我已经阅读了足够让我入门但我遇到了这个障碍：我应该重用我的现有的视图，将EF直接连接到它们，还是应该只连接到真实的表格，然后在我的应用程序中重新创建这些视图？
一方面，我有一个很多我想重用的视图来快速启动我的应用程序开发。另一方面，我直接连接到视图而不是表时听到了严重的性能问题，特别是包含其他视图的视图和性能在我的新应用程序中将是最重要的，因为excel文件变得非常慢。
你能告诉我最好的行动方案，记住我需要尽可能最好的表现吗？
我尝试了什么：
我无法决定是否在我的应用程序中使用视图
Hi,
I realize my question is a little bit conceptual, but I need this sorted before I move on with my project.
I've created dozens of views in SQL, some of which are pretty complex involving more than 12 tables. I use these views in a business report excel file to do some business intelligence.
I'm now trying to migrate that excel report into a full-grown application in c# using wpf, mvvm pattern and the entity framework.
I believe I've read enough to get me started but I've come across this hurdle: should I reuse my existing views, connecting EF directly to them or should I connect only to the real tables instead and recreate those views in my application?
On the one hand, I have a lot of views which I want to reuse to jumpstart my application development. On the other hand, I've heard of serious performance issues when connecting directly to views instead of tables, particularly views which contain other views and performance will be paramount in my new application, because the excel file is getting terribly slow.
Can you advise me on the best course of action, keeping in mind that I need the best performance possible?
What I have tried:
I can't decide whether to go with views or not in my application
推荐答案
这篇关于我应该使用现有的复杂视图还是在我的应用程序中重新创建查询？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！