If you use a DAL generation technology like SubSonic or use linq in your code it shouldn’t matter what your DB is.
MS Access is free but it sucks no serious developer should ever use this.
MySQL is free and maybe lacking in a few features but it is a valid alternative if you don’t want to shell out cash for SQL Server.
Oracle is a huge pain in the butt. Don’t use it with .Net technologies unless absolutely necessary. It is like hitting a railway spike with a train that needs 30 people to make sure it stays on the tracks. Or like some other crazy analogy. You can’t do simple things like declare a boolean column or set a primary key column as identity. You have to do everything manually and you have to endlessly muck around with triggers. After the initial set up costs it gets cheaper to use but the initial set up costs are pretty big. Also the documentation is sparse and the error codes are as cryptic as they come.
M$ SQL Server is quite simply amazing. Don’t take it for granted. Flexible, scalable and easy to use. Books online is your best friend.
SQL Server 2005/2008, or the express version if your database is small are good choices with asp.net and c#. If you use VS2008 or visual web developer, you drop a sql connection and a control and the code is generated. the code is even pretty efficient. the ado .net framework has a very powerful sqlclient api.
access is a single use database. people tried often but sooner or later something will go wrong with locks.
i agree with the other person’t assessment about oracle: very costly, not at all well integrated with the .net framework, and lots of sql server features missing. (i used oracle for 5 yrs).
mysql may work but it is not a high performance transaction oriented database. it deoends. if you store text and pics, maybe mysql will work
Comments
Leave a comment Trackback