我的应用程序。是在 C# 3.5 和 MySQL 5.1 中。它是一个基于 Windows 的独立应用程序。它自过去两年以来一直成功运行，除了一些问题之外，后来发现也是 MySQL 的错误。该错误扰乱了实时报告，因为它在两行中存储了相同的时间戳。
我不知道 MySQL 是否修复了它，所以我想摆脱它。现在的选项有：
SQL Server 2005/2008 Express、Oracle 10g Express、DB2 9.2 Express、PostgreSQL、MS Access 或 SQLite。
从明显的选择开始：MS Access 和 MS Access SQLite。 MS Access 的问题是 MDB 因突然断电而损坏，并且文件不可修复。这发生在我们的生产数据库上。
SQLite 的问题在于它的 GUI 仍然没有丰富的查询浏览器，而且您无法通过 GUI 创建组合键。其次，我从来没有使用过它，不能冒险。我不知道它支持多少约束。
剩下的就来了。 SQL Server 很好，但是 SO 的人说它有自己的一组错误。它还限制数据库大小。 Oracle，即使是 Express Edition，如果出现问题，迟早需要 DBA。
我没有使用过 IBM DB2，但人们说它是一个非常强大的数据库，而且它的 GUI 功能丰富。除此之外，它非常易于管理并且没有大小限制。 PostgreSQL 也是如此，但 GUI 功能不是那么丰富，但也足够了。我不知道它的许可是如何运作的。另一个问题是它的.NET 连接器速度不快。与 ODBC 连接器相比，它的运行速度较慢。
欢迎您提出宝贵的见解和建议。
My app. is in C# 3.5 and MySQL 5.1. It is a Windows based standalone application. It is running successfully since last two years except few issues and that too were later found out to be MySQL bugs. The bug disturbed the real-time reports as it store the same timestamp in two rows.
I don't know whether MySQL fixed it or not so I want to get rid of this. Now the options are:
SQL Server 2005/2008 Express, Oracle 10g Express, DB2 9.2 Express, PostgreSQL, MS Access or SQLite.
Starting with the obvious choices: MS Access & SQLite. The problem with MS Access is that the MDB gets corrupted is a sudden power failure occurs and the file is not repairable. This happened with us on a production DB.
The problem with SQLite is that it's GUI still doesn't have rich query browser and also you cannot create composite keys through GUI. Secondly, I never used it and can't take chance. I don't know how many constraints it supports.
Coming to the rest. SQL Server is good, but people here at SO said that it has its own set of bugs. Also it limits database size. Oracle, even though Express Edition, needs sooner or later a DBA, if something goes wrong.
I have not used IBM DB2 but people say that it is a very robust database and its GUI is feature rich. Apart from that it is very easy to manage and has no size limits. Same is true with PostgreSQL, but GUI not so feature rich, however it is sufficient. I don't know how it's licensing works. The other problem is that its .NET connector is not fast. It works slow as compared to its ODBC connector.
Your valuable insights and recommendations are welcome.
发布评论
评论（2）
由于您因数据大小有限而排除了 Access 和快速添加，因此即使您没有排除其他方法，也没有理由不使用 Postgres。请参阅我对下面问题的回答以及其他人的回答。
超出 2GB 限制的 SQL Server Express 替代方案
Cystal 报告
http://wiki.postgresql.org/wiki/PostgreSQL_and_Crystal_Reports
Being you ruled out Access and express additions for their limited data size there is really no reason not to use Postgres even if you hadn't ruled the others out. See my answer to the question below along with the others who answered.
SQL Server Express alternatives beyond 2GB limit
Cystal Reports
http://wiki.postgresql.org/wiki/PostgreSQL_and_Crystal_Reports
我在 IBM 从事 DB2 LUW 工作，所以我当然有偏见，但如果您确实决定尝试一下 DB2，这里有关于 在 Visual Basic 中构建 .NET 应用程序和带有编译和链接选项的 C#。
I work at IBM on DB2 LUW, so of course I'm biased, but if you do decide to give DB2 a try here's the details on Building .NET applications in Visual Basic and C# complete with compile and link options.