刚接触 sharepoint 开发，列表会取代您的数据库吗？
我们刚刚开始 Sharepoint 开发，我的首要任务之一是构建一个数据收集工具。它将跨多个站点使用，因此会有一个管理区域，每个站点都会拉入相关问题，并记录数据。我已经阅读了很多有关开发的教程，并且非常清楚如何开始。我只是想确保我明白一件事。列表基本上取代了您的数据库吗？如果这是一个常规应用程序，我将创建一个问题表、一个链接表（告诉哪些问题连接到哪个站点）、一个存储答案、链接到站点和问题表的表。
这是您遵循的基本模式，还是我应该对 Sharepoint 应用程序采取不同的做法？
如果想法是使用外部数据库，任何人都可以向我指出一些有关此的信息吗？
We're just starting Sharepoint development, and one of my first tasks is to build a data collection tool. It will be used across multiple sites, so there will be an admin area, and each site will pull in it's related questions, and record the data. I've gone through a bunch of tutorials on development, and have a fairly good idea of how to start. I just want to make sure I understand one thing. Do lists basically take the place of your database? If this was a regular app, I would create a question table, a link table that tells which questions are connected to which site, a table that stores the answer, linking to the site and question table.
Is this the basic pattern you follow, or should I be doing things differently for Sharepoint applications?
If the thought is to use an external databse, can anyone point me to some info on this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在我们的 Sharepoint 项目中，我们主要关注列表。从某种程度上来说，这很好 - 直到 DB 数据之间只有很少的关系。添加表和关系后，性能下降很多，我们不得不改用 MS SQL Server 中的标准数据库。所以我推荐使用DB。
缺点：无法使用共享点控件来编辑/查看数据，并且无法从共享点级别限制对数据的访问
优点：更快地访问数据
In our Sharepoint project we stared with Lists. It was good to some point - till DB had only few relations between data. After adding tables and relations performance falls a lot and we had to switch to use standard DB in MS SQL Server. So I recomend to use DB.
Disadventages: you cannot use sharepoint controls to edit/view data and cannot restrict access to data from sharepoint level
Adventages: much faster access to data