自定义数据库与 MOSS 2007 集成
希望以前有人走过这条路，并且可以就我应该走的方向提供一些合理的建议。我目前参与的一个项目中，我们将利用自定义数据库来存储根据预先建立的模板从 Excel 文件中提取的数据（以保持一致性）。我们目前有一个流程（用 C#.Net 2008 编写），可以从电子表格中提取必要的数据并将其导入到我们的自定义数据库中。我主要感兴趣的是找出将该流程与我们的门户集成的最佳方法。我想要做的是让 SharePoint 跟踪有关电子表格本身的元数据，并让自定义数据库跟踪电子表格中包含的数据。因此，我需要一种将电子表格从 SharePoint 链接到自定义数据库的方法，反之亦然。由于这些电子表格将定期更新，因此我需要经过尝试且真实的方法来确保数据在 SharePoint 和自定义数据库之间保持同步。我还想了解如何使用自定义数据库中的数据在 SharePoint 门户中创建报告。任何和所有信息将不胜感激。
Hopefully someone has been down this road before and can offer some sound advice as far as which direction I should take. I am currently involved in a project in which we will be utilizing a custom database to store data extracted from excel files based on pre-established templates (to maintain consistency). We currently have a process (written in C#.Net 2008) that can extract the necessary data from the spreadsheets and import it into our custom database. What I am primarily interested in is figuring out the best method for integrating that process with our portal. What I would like to do is let SharePoint keep track of the metadata about the spreadsheet itself and let the custom database keep track of the data contained within the spreadsheet. So, one thing I need is a way to link spreadsheets from SharePoint to the custom database and vice versa. As these spreadsheets will be updated periodically, I need tried and true way of ensuring that the data remains synchronized between SharePoint and the custom database. I am also interested in finding out how to use the data from the custom database to create reports within the SharePoint portal. Any and all information will be greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
实际上，我也在 SharePoint 中为一家大型金融机构编写了类似的系统。
我们解决这个问题的方法是在文档库上有一个事件接收器。每当上传或更新文件时，都会触发事件接收器，我们使用 Aspose.Cells。
将 Excel 工作表中的数据与数据库中的数据进行匹配的关键是隐藏工作表中的一个小标题，其中包含有关报告期间和数据类型的信息。您还可以使用 SharePoint 项目的唯一 ID 作为键或文件的完整路径。这完全取决于系统的使用方式和您的具体要求。
I have actually written a similar system in SharePoint for a large Financial institution as well.
The way we approached it was to have an event receiver on the Document library. Whenever a file was uploaded or updated the event receiver was triggered and we parsed through the data using Aspose.Cells.
The key to matching data in the excel sheet with the data in the database was a small header in a hidden sheet that contained information about the reporting period and data type. You could also use the SharePoint Item's unique ID as a key or the file's full path. It all depends a bit on how the system will be used and your exact requirements.
我想这可能会很尴尬。业务数据目录 (BDC) 功能将使您能够与数据库紧密集成，但同时尝试与单独的电子表格保持永久同步可能会很棘手。我想您可以通过捕获处理电子表格本身的文档库的更新事件，然后将正确的信息推送到数据库中来做到这一点。但是，如果您打算这样做，我不清楚为什么您不能只选择其中之一：
如果您选择#1，那么您仍然可以能够在文档本身中搜索并轻松更新它们。如果您选择#2，则不必担心在初始加载后与实际工作表同步，并且您可以（例如）根据需要创建表单以允许人们修改数据。
此外，根据您的使用案例，您可能会受益于 MOSS 服务器端 Excel 服务。我认为这里的“正确”决定可能需要更多信息来了解您和您的团队在最初上传到您的 SharePoint 世界之后希望如何与这些工作表和数据进行交互。
I think this might be awkward. The Business Data Catalog (BDC) functionality will enable you to tightly integrate with your database, but simultaneously trying to remain perpetually in sync with a separate spreadsheet might be tricky. I guess you could do it by catching the update events for the document library that handles the spreadsheets themselves and subsequently pushing the right info into your database. If you're going to do that, though, it's not clear to me why you can't choose just one or the other:
If you go with #1, then you still have the ability to search within the documents themselves and updating them is painless. If you go with #2, you don't have to worry about sync'ing with an actual sheet after the initial load, and you could (for example) create forms as needed to allow people to modify the data.
Also, depending on your use case, you might benefit from the MOSS server-side Excel services. I think the "right" decision here might require more information about how you and your team expect to interact with these sheets and this data after it's initially uploaded into your SharePoint world.
所以...我假设您正在利用 Excel，因为它是定义、构建和测试所需数学的简单方法。您的电子表格有一组输入数据元素、一堆数学元素，然后还有一些输出元素。您是否考虑过使用 Excel Services？在这种情况下，您将避免运行批处理来生成输出元素。相反，您可以直接在 SharePoint 中调用 Excel 服务并运行计算。更多信息：可在线获取。
您还可以直接从电子表格在 SharePoint 中显示信息。例如，如果电子表格中有一个图表，您可以链接到该图表并公开它。当数据发生变化时，图表也会发生变化。
Microsoft 在不久的将来还会推出一些高性能计算 (HPC) Excel 选项。如果您的电子表格非常非常大，那么 Excel Services 路线可能不起作用。网上有一些信息（搜索 HPC excel - 我无法发布链接）。
So... I'm going to assume that you are leveraging Excel because it is an easy way to define, build, and test the math required. Your spreadsheet has a set of input data elements, a bunch of math, and then there are some output elements. Have you considered using Excel Services? In this scenario you would avoid running a batch process to generate your output elements. Instead, you can call Excel services directly in SharePoint and run through your calculations. More information: available online.
You can also surface information in SharePoint directly from the spreadsheet. For example, if you have a graph in the spreadsheet, you can link to that graph and expose it. When the data changes, so does the graph.
There are also some High Performance Computing (HPC) Excel options coming out from Microsoft in the near future. If your spreadsheet is really, really big then the Excel Services route might not work. There is some information available online (search for HPC excel - I can't post the link).