Our company has an ASP.NET application for customer information database. The application started small but has grown without proper design. Now a new version of the app should be developed, which basically would mean designing and implementing it from scratch. The company is interested in making use of Microsoft Sharepoint Services in future and it has been suggested to pilot it with this customer database application.
我们公司有一个客户信息数据库的ASP.NET应用程序。应用程序开始很小,但没有适当的设计增长。现在应该开发一个新版本的应用程序,这基本上意味着从头开始设计和实现它。该公司有兴趣在未来使用Microsoft Sharepoint Services,并建议使用此客户数据库应用程序进行试用。
So my questions is:
所以我的问题是:
Is database driven application something WSS is good for? Mostly the app would perform CRUD-operations on the database and also create reports.
数据库驱动的应用程序是WSS有用的东西吗?大多数应用程序将对数据库执行CRUD操作并创建报告。
4 个解决方案
#1
I agree with Greg in that I wouldn't necessarily recommend putting your data in SharePoint lists (this is what Greg may be assuming). But my short answer would be "maybe".
我同意Greg的意见,因为我不一定会建议将您的数据放入SharePoint列表中(这是Greg可能会假设的)。但我的简短回答是“也许”。
Here's the long answer...
这是一个很长的答案......
SharePoint runs on ASP.NET so it should accommodate your needs. You would likely be writing ASP.NET web pages that live within SharePoint that access your database or writing web parts that live within SharePoint that access your database.
SharePoint在ASP.NET上运行,因此它可以满足您的需求。您可能正在编写位于SharePoint中的ASP.NET网页,这些网页访问您的数据库或编写访问数据库的SharePoint内部的Web部件。
You could consider the BDC for reading/retrieving data, but that requires MOSS Enterprise and won't provide the CUD part of CRUD. Other tools like CorasWorks DIT may help, but I suspect that custom web parts or pages are the way to go for you.
您可以将BDC视为读取/检索数据,但这需要MOSS Enterprise,并且不会提供CRUD的CUD部分。像CorasWorks DIT这样的其他工具可能会有所帮助,但我怀疑自定义Web部件或页面是您的最佳选择。
There are plenty of benefits you can get from SharePoint such as authorization and maybe things like integration of your data with SharePoint list data, provisioning, search, etc. It really depends on the nature of your application as to whether SharePoint will provide much of a benefit.
您可以从SharePoint获得许多好处,例如授权,以及诸如将数据与SharePoint列表数据集成,供应,搜索等等。这实际上取决于应用程序的性质,即SharePoint是否会提供大量的效益。
#2
Short answer: No.
简答:没有。
Long answer: Is there any collaboration? Supporting documentation for the data? Workflow? If no, then there really isn't any reason to host it through SharePoint - you won't be gaining much.
答案很长:有合作吗?支持数据文档?工作流程?如果不是,那么确实没有任何理由通过SharePoint托管它 - 你将不会获得太多收益。
Additionally, keep in mind that the SharePoint lists may look like tables, but they aren't - there is no relational aspects of the lists - no joining, no cascading updates/deletes, etc. This may be a problem if data reporting is a big part of your app.
此外,请记住,SharePoint列表可能看起来像表,但它们不是 - 列表没有关联方面 - 没有加入,没有级联更新/删除等。如果数据报告是一个问题,这可能是一个问题。你的应用程序的重要部分。
You can store the data externally and have it appear as read-only lists in SharePoint, but you're still jumping through a lot of hoops if you're not using any of the other SharePoint features.
您可以在外部存储数据并使其在SharePoint中显示为只读列表,但如果您不使用任何其他SharePoint功能,那么您仍然会遇到很多问题。
#3
Kirk beat me to punch and said it better than I would have anyway :)
Kirk打我一拳,说它比我还要好:)
Another thing to consider is the possiblity of workflows in your process. For example, if you need to start a process when a new contact is added (a follow-up call, etc.), then SharePoint provides a great deal or benefit.
另一件需要考虑的事情是您的流程中工作流程的可能性。例如,如果您需要在添加新联系人(后续呼叫等)时启动流程,则SharePoint可提供大量优势或优势。
Perhaps a hybrid solution would be appropriate. A custom app for your CRUD and SharePoint integration for the pieces that make sense and provide value.
也许混合解决方案是合适的。适用于CRUD和SharePoint集成的自定义应用程序,用于有意义且有价值的部分。
Building in SP for the sake of using SP probably isn't a good idea.
为了使用SP而在SP中构建可能不是一个好主意。
#4
We have an ASP.NET application that runs in MOSS 2007. While we barely use any of SharePoint's features, we do get the advantage of SharePoint's security model, navigation webparts (we use CorasWorks), integrated Reporting Services, and workflows. In the very least, SharePoint features are there for us to use someday.
我们有一个在MOSS 2007中运行的ASP.NET应用程序。虽然我们几乎没有使用任何SharePoint的功能,但我们确实利用了SharePoint的安全模型,导航webparts(我们使用CorasWorks),集成的Reporting Services和工作流程。至少,有一天我们可以使用SharePoint功能。
All of our application data is in its own SQL Server database. We don't store anything in the SharePoint content database.
我们所有的应用程序数据都在自己的SQL Server数据库中。我们不会在SharePoint内容数据库中存储任何内容。
#1
I agree with Greg in that I wouldn't necessarily recommend putting your data in SharePoint lists (this is what Greg may be assuming). But my short answer would be "maybe".
我同意Greg的意见,因为我不一定会建议将您的数据放入SharePoint列表中(这是Greg可能会假设的)。但我的简短回答是“也许”。
Here's the long answer...
这是一个很长的答案......
SharePoint runs on ASP.NET so it should accommodate your needs. You would likely be writing ASP.NET web pages that live within SharePoint that access your database or writing web parts that live within SharePoint that access your database.
SharePoint在ASP.NET上运行,因此它可以满足您的需求。您可能正在编写位于SharePoint中的ASP.NET网页,这些网页访问您的数据库或编写访问数据库的SharePoint内部的Web部件。
You could consider the BDC for reading/retrieving data, but that requires MOSS Enterprise and won't provide the CUD part of CRUD. Other tools like CorasWorks DIT may help, but I suspect that custom web parts or pages are the way to go for you.
您可以将BDC视为读取/检索数据,但这需要MOSS Enterprise,并且不会提供CRUD的CUD部分。像CorasWorks DIT这样的其他工具可能会有所帮助,但我怀疑自定义Web部件或页面是您的最佳选择。
There are plenty of benefits you can get from SharePoint such as authorization and maybe things like integration of your data with SharePoint list data, provisioning, search, etc. It really depends on the nature of your application as to whether SharePoint will provide much of a benefit.
您可以从SharePoint获得许多好处,例如授权,以及诸如将数据与SharePoint列表数据集成,供应,搜索等等。这实际上取决于应用程序的性质,即SharePoint是否会提供大量的效益。
#2
Short answer: No.
简答:没有。
Long answer: Is there any collaboration? Supporting documentation for the data? Workflow? If no, then there really isn't any reason to host it through SharePoint - you won't be gaining much.
答案很长:有合作吗?支持数据文档?工作流程?如果不是,那么确实没有任何理由通过SharePoint托管它 - 你将不会获得太多收益。
Additionally, keep in mind that the SharePoint lists may look like tables, but they aren't - there is no relational aspects of the lists - no joining, no cascading updates/deletes, etc. This may be a problem if data reporting is a big part of your app.
此外,请记住,SharePoint列表可能看起来像表,但它们不是 - 列表没有关联方面 - 没有加入,没有级联更新/删除等。如果数据报告是一个问题,这可能是一个问题。你的应用程序的重要部分。
You can store the data externally and have it appear as read-only lists in SharePoint, but you're still jumping through a lot of hoops if you're not using any of the other SharePoint features.
您可以在外部存储数据并使其在SharePoint中显示为只读列表,但如果您不使用任何其他SharePoint功能,那么您仍然会遇到很多问题。
#3
Kirk beat me to punch and said it better than I would have anyway :)
Kirk打我一拳,说它比我还要好:)
Another thing to consider is the possiblity of workflows in your process. For example, if you need to start a process when a new contact is added (a follow-up call, etc.), then SharePoint provides a great deal or benefit.
另一件需要考虑的事情是您的流程中工作流程的可能性。例如,如果您需要在添加新联系人(后续呼叫等)时启动流程,则SharePoint可提供大量优势或优势。
Perhaps a hybrid solution would be appropriate. A custom app for your CRUD and SharePoint integration for the pieces that make sense and provide value.
也许混合解决方案是合适的。适用于CRUD和SharePoint集成的自定义应用程序,用于有意义且有价值的部分。
Building in SP for the sake of using SP probably isn't a good idea.
为了使用SP而在SP中构建可能不是一个好主意。
#4
We have an ASP.NET application that runs in MOSS 2007. While we barely use any of SharePoint's features, we do get the advantage of SharePoint's security model, navigation webparts (we use CorasWorks), integrated Reporting Services, and workflows. In the very least, SharePoint features are there for us to use someday.
我们有一个在MOSS 2007中运行的ASP.NET应用程序。虽然我们几乎没有使用任何SharePoint的功能,但我们确实利用了SharePoint的安全模型,导航webparts(我们使用CorasWorks),集成的Reporting Services和工作流程。至少,有一天我们可以使用SharePoint功能。
All of our application data is in its own SQL Server database. We don't store anything in the SharePoint content database.
我们所有的应用程序数据都在自己的SQL Server数据库中。我们不会在SharePoint内容数据库中存储任何内容。