本文介绍了何时从电子表格切换到RDBMS?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我自愿与一个非政府组织合作,帮助他们在其社区中心保存记录。目前,只有一个社区中心,其中所有的数据都存储。但是,这预计会在年底前发生变化。



目前,他们的数据是使用两张工作簿来维护的。主表中的每个记录可以在后续表中具有多达100个跟踪。数据结构松散,没有明确的约束。



将所有现有数据从电子表格移动到RDBMS需要付出努力,但我愿意这样做;特别是因为有人说这些数据可以与现场的其他非政府组织共享。



一种替代方法是使用例如Google文档,并合并每一组记录手动。



有多个数据输入和检索点,推荐从电子表格数据库转移到RDBMS是否有意义?



编辑
只是发布了一个策略的后续跟踪

解决方案

移动到RDBMS,该RDBMS用于处理在正确的表格中结构化的数据。



当电子表格指向彼此并且它们只是保持在增长,RDBMS处理好的东西。



移动(估计,不要使用电子表格



脚注:出于对可用性的考虑,我已经很容易,因为它已经很好的组织了,你在处理这个问题之前,它是一个问题。将允许用户挂在一个类似于他们现在,GUI的解决方案。您可以通过csv或其他文件格式(例如Google文档或MS Excel)将导出/导入数据 导入到RDBMS ,速度和索引等。



有一个很好的文章,它强调了使用的区别: p>


  • quick& dirty:go for spreadsheets

  • 可维护性&长期存储:去数据库


I've volunteered with a Non-Governmental Organization to help with their record-keeping at their community centre. At present, there is only one community centre where all their data is stored. However, this is expected to change by the end of the year.

Presently their data is maintained using a workbook with two sheets. Each record in the main sheet may have upto 100 follow-ups in the follow-up sheet. Data is loosely structured, and there are no explicit constraints.

Moving all existing data from a spreadsheet to an RDBMS would require effort, but I'm willing to do that; particularly since there is talk of making said data shareable with other NGO in the field.

One alternative would be to use, say, Google Docs, and merge each set of records manually.

With more than one point of data entry, and retrieval, does it make sense to recommend moving away from a spread-sheet database to an RDBMS?

EDITJust posted a follow-up on strategy to follow here

解决方案

Yes it does make sense to move to an RDBMS, which is made for handling data structured in just that, tables.

Things tend to be messy when having spreadsheets referring to each other and they just keep on growing, something an RDBMS handles well. You could add features via SQL such as complex formulas in a much more simple way than with spreadsheets.

The move (estimating, don't know enough about the data) seems easy since it's already well organized and you are dealing with this problem before it even is a problem.

Footnote: out of usability concerns, I would allow the users to hang on to a similiar solution as they have now, GUI-wise. You can export/import data to, for example Google Docs or MS Excel, via csv or other file formats, which still allows you to have the backend in an RDBMS for maintainability, speed and indexing etc.

There is a nice article on http://www.cazh1.com/blogger/thoughts/2007/03/excel-vs.shtml which emphasizes just that differentiation of use:

  • quick & dirty: go for spreadsheets
  • maintainability & long-term-storage: go for a database

这篇关于何时从电子表格切换到RDBMS?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-27 16:27