决定数据库需求
我有出售的小型 .net 应用程序。 我使用 Access 作为数据库，但我认为它不够灵活和快速。另外，我计划启用网络数据库访问，因此我需要建议移动哪个数据库系统。
我的程序是一个商店销售组织者，我记录商店的每笔销售。我需要数据库中的客户、库存、销售记录。一些客户一个月内销售额达到 10,000 件，产品数量约为 100,000 件。
编辑：
此外，数据库系统必须易于管理且易于备份。
I have small .net application which I sell.
I was using Access as database but I think it's not flexible and fast enough. Also I'm planning to enable network database access so I need suggestions which database system to move.
My program is a shop sales organizer and I record every sale on a shop. I need customer, stock, sale records in the database. Some clients make 10k sales and about 100k products in a month.
EDIT:
Also the database system must be easy to manage and easy to backup.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
如果你想要零配置，我推荐嵌入式数据库SQLite。它体积小、高效、可靠且免费。
您不必经历在用户计算机上设置数据库服务器的麻烦，并且只要您没有大量流量，就可以在网络设置中很好地工作。
If you want zero configuration, I'd recommend the embedded database SQLite. It is , small, efficient, reliable, and free.
You don't have to go through the trouble of setting up a db server on the users machine and as long as you don't have tons of traffic, works well in a networks setup.
我不确定您如何得出当前使用 Access 文件的配置不够的结论。请注意所有通常以“我从 2.0 开始就没有使用过 Access，但我记得有一些问题。等等，等等”这样开头的 Access 恐怖故事。与因为 Win95 遇到的崩溃而评判 Windows 7 一样糟糕。
似乎您的客户使用较大的数据集会发现明显的性能问题，或者您的产品遇到了太多您归因于数据文件的错误。似乎与过早的扩展相比，客户会更欣赏其他特性和功能。
您提到了 SQL Server CE。它可以像 Express 一样处理多达 4 GB 的数据。两者都可以通过您的安装包进行部署。 CE 的安装要小得多：1.8mb vs 197mb。两者都提供 Transact-SQL，但 CE 缺乏过程 T-SQL 以及存储过程、视图和触发器（我认为这是不使用它的一个重要原因。）。 Express是基于服务器的，具有更多的服务功能。通过拒绝用户直接访问数据文件可能会更安全，并且使事情变得更容易提供基于角色的安全性。 CE 文件是文档安全的，因为它们没有代码，您可以创建自己的特定于您的应用程序的文件扩展名。我猜您的应用程序大部分时间都在已安装的计算机上运行，因此始终运行 SQL Express 服务的开销可能会也可能不会成为问题。零售商店似乎不使用高性能硬件。你可能想要一些更清淡的东西。
没有一种转换是完美的。根据您开发应用程序的方式，坚持使用 MS 产品可能会更容易。这一切都取决于。
I'm not sure how you came to the conclusion that your current configuration using an Access file isn't sufficient. Beware of all the Access horror stories that usually start with, "I haven't used Access since 2.0, but I recall some problem. with, blah, blah, blah." About as bad as judging Windows 7 because of some crash you experienced with Win95.
Seems like a noticable performance problem by your clients with larger datasets would have been recognized or your product is experiencing too many errors that you attribute to the data file. Just seems like there would be other features and functionality that clients would appreciate a lot more over premature scaling.
You mentioned SQL Server CE. It can handle up to 4 gigs of data just like Express. Both can be deployed with your installation package. CE's installation is much smaller: 1.8mb v 197mb. Both offer Transact-SQL, but CE lacks Procedural T-SQL as well as stored proc, views and triggers (A big reason not to use it IMO.). Express is server based and has more service features. It's probably more secure by denying users direct access to the data files and to make things easier offers Role-based security. CE files are document safe since they have no code and you could create your own file extension that is specific to your application. I'm guessing your app runs most of the time on the installed machines so having the over-head of SQL Express service running all the time may or may not be a problem. Retail shops don't seem to use high-performance hardware. You may want something lighter.
No conversion is perfect. Depending on how you've developed your application, sticking with a MS product may be easier. It all depends.
MySQL是一个不错的选择。我相信较新的版本（最终）允许严格执行外键。我在很多场合都使用过这个。如果您要重新分发系统（以便用户可以建立自己的销售店），我强烈推荐
sqlite。它速度快、免费，并且一直越来越受欢迎。现在所有主要编程语言都有 API。此外，如果您的项目需要考虑的话，还有一些方法可以在网络服务器上运行它。MySQLis a great choice. And I believe newer versions (finally) allow for strictly enforced foreign keys. I have used this on many occasions.If you will be redistributing your system (so users can set up their own sales shop), I highly recommend
sqlite. It's fast, free, and growing in popularity all the time. There are now APIs for all major programming languages. Also, there are ways to run it on a webserver, if that's a consideration for your project.MySQL 快速、小型、高效、可靠且免费。我会推荐它。
MySQL is fast, small, efficient, reliable, and free. I'd recommend it.
是什么让您觉得 Access 不够灵活或不够快？ Access 也适用于网络上的多个用户。
请注意，Access 的数据库引擎部分和 Access 的 UI 部分之间存在差异，后者允许您创建查询、表单、报告、nacros 和 VBA 代码。这里的许多发帖者在回复中只提到了数据库引擎部分。
What makes you feel Access is not flexible or fast enough? Access also works well with multiple users on a network.
Note that there is a difference between the database engine portion of Access and the UI portion of Access which allows you to create queries, forms, reports, nacros and VBA code. Many of the posters here have only mentioned the database engine portion in their reply.
什么不灵活，屏幕、报告、程序？.. 有多少：并发用户？.. 每秒事务数？不要忘记，您可以将 SQL 引擎与 access 和 jet 一起使用，而 access 的最佳功能是与 excel、word 和其他模块的集成。如需访问功能，请访问：
链接文本 http://office.microsoft.com/en-我们/access/access-2010-features-and-benefits-HA101809011.aspx
what's not flexible, the screens, reports, procedures?.. How many: concurrent users?.. transactions per second? Don't forget that you can use SQL engine with access vs. jet, and the best of feature of access is the integration with excel, word and other modules. for access features visit:
link text http://office.microsoft.com/en-us/access/access-2010-features-and-benefits-HA101809011.aspx