从Access升级到？ [英] Upsize from Access to?

问题描述

我有一个用于收集医疗记录的应用程序，它已经包含了几条100k的记录。它非常棒，感谢Neopa，Adezi和其他聪明人提供的大力帮助。


我的问题：在明年我将不得不推出更多站点和收集的所有数据将在站点导出，并通过本地网络导入中央服务器，可能有+ -10人可以访问数据。

我应该只升级后端数据库到SQL服务器，或者前端当前也在Access 2007中，需要用另一种语言重写。为了防止我的应用程序早日死亡？


我担心Access将无法处理数百万条记录。


有什么建议吗？

I have an application that is used to collect medical records and it consists of a few 100k records already. It works great, thanks to the great assistance i have had from Neopa, Adezi and the other clever guys.

My question: in the next year i will have to roll out to many more sites and all the data collected will be exported at site, and imported onto a central server, with perhaps +-10 persons having access to the data, via a local network.
Should i just upgrade the Backend database to a sql server, or does the front-end currently also in Access 2007, needs to be rewritten in another "language" to prevent an early death of my "application"?

My worry is that Access will not be able to deal with millions of records.

Any suggestions please?

推荐答案

拆分数据库会很好用 - 后端将处理2GB数据访问2007规范。至于这将包含多少记录，这取决于表和链接的数量等...我有一个链接到网站有一些粗略的数字，丢失它，我会看到我是否能找到它今天晚些时候。


有了这样的说法，使用拆分数据库扩大SQL-Server之类的功能将会带来一些痛苦;但是，没有你想象的那么多：使用调整大小向导将访问数据移动到SQL Server数据库

请注意，这只是表面上的问题，你不会使用SQL-Server，你可以想象将后端移动到Oracle服务器，只需对代码中的ODBC驱动程序和连接进行一些调整 - 无论你在后端采用哪种方式，你都会得到很多帮助。

The split database will be good for good while -the back-end will handle 2GB of data Access 2007 specifications. As to how many records this will hold, that depends on the number of tables and links and the like.... I had a link to site that had some rough numbers, lost it, I''ll see if I can find it later today.

With that said, up-sizing to something like SQL-Server with a split database will involve some pain; however, not as much as you would expect: Move Access data to a SQL Server database by using the Up-sizing Wizard

Mind you this only scratches the surface and you''re not stuck using SQL-Server, you could conceivably move the back-end to an Oracle server, just a few tweaks to the ODBC drivers and connections within the code - and you''ll have plenty of help here no matter which way you go for the backend.

Thx zmbd。我一直在想什么是最好的软件，从头开始学习，当我重写FE - 即VB.net或C ++或其他什么，然后显然是要链接的BE。将当前数据从Access迁移到无论什么但很重要。

有什么建议吗？

Thx zmbd. i have been thinking what would be the best software to learn from scratch, when i rewrite the FE - ie VB.net or C++ or whatever, and then obviously the BE to link to. Migration of the current data from Access to "whatever" is important however.
Any suggestions?

将BE更改为几乎所有成熟的数据库服务器应该很简单。然而，改变FE完全是另一回事。访问并不像没有任何东西那么受欢迎。使用另一种语言重现逻辑并且没有使用Access内置的所有花哨功能所涉及的工作将远远超过从头开始访问Access。在采取任何这样的步骤之前，我会敦促认真谨慎。可能首先要知道你在其他一些不太重要的项目中处理什么。您可能会发现，您需要做大量的工作才能提供在Access中工作时习惯使用的基础知识。

Changing the BE to almost any grown-up database server should be straightforward enough. Changing the FE however, is another matter entirely. Access isn''t as popular as it is for nothing. The effort involved in reproducing the logic in another language and without all the bells and whistles built in as you have with Access, will be a lot more than starting Access from scratch. I would urge serious caution before taking any such step. Possibly get to know what you''re dealing with inside a few other, less important, projects first. You will probably find you need a great deal of work just to provide the basics that you''re used to having available when working within Access.

这篇关于从Access升级到？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！