4 ms·
> If you go with MySQL or PostgreSQL, be prepared to fix bugs in the ADO connectors from .Net to the database. Likewise for SQL Server and ODBC, but then the b
by dfranke 19y ago
> If you go with MySQL or PostgreSQL, be prepared to fix bugs in the ADO connectors from .Net to the database.
Likewise for SQL Server and ODBC, but then the bugs are in SQL Server so you can't fix them. However, .NET has a perfectly good ODBC client library. Use that, not ADO, to talk to MySQL.
- kogir 19y agoIf you find a legitimate bug in SQL Server, you can open a support ticket, and Microsoft will fix it. Frequently these fixes will make it into the next service pack, or if they're severe, a Windows update. This is all at no (extra) cost to you. In speed tests I've seen using ODBC be as much as 10x slower than npgsql in talking to PostgreSQL. I didn't look into why, and just used ADO.Net.
- dfranke 19y agoI don't think I ever encountered a bug for which I'd be able to write a coherent support ticket. They tended to be horrendous mandelbugs that were difficult to reliably reproduce due to caching. If it were an open source project then I could have at least set some watchpoints and sent a useful backtrace, but with closed source, SOL.
- watmough 19y agoOracle has a native driver for .NET. Google for ODP.NET. If it's anything like as good as their pure Java JDBC drivers, it will perform pretty well.