I've been looking into a lot of database's recently, and am not sure if it's because I'm bored or what, but I want to create a few web applications using database's other than MS SQL Server. Any suggestions that tie into ASP.NET nicely?
+1 I agree. Both have .net providers so all the code you are used to writing with sql will be the same except specific for these databases.
spinon
2010-07-03 06:23:31
true. both have reliable .net providers. only difference is vistaDB is commercial but its worth the cost.
this. __curious_geek
2010-07-03 11:39:17
+2
A:
I suggest you take a look at Connectionstrings.com. Most databases there have a .NET provider available.
XIII
2010-07-03 07:03:40
+3
A:
I'd consider MySQL as the obvious alternative.
However, fundamentally one relational database is pretty much the same as another, more so when accessed through something like ADO.NET. If you're bored with SQL Server then rather than looking for an alternative why not look at trying different data access strategies?
You don't mention whether or not you're using an ORM (object relational mapper) which can make working with databases a lot more enjoyable than using standard ADO.NET, such as:
- NHibernate
- Entity Framework
- Linq to SQL
- Subsonic
IMO, sticking with SQL Server but trying out a few different ORM's would be much more interesting than switching to a different database altogether.
Or how about looking into using a document database, such as RavenDB?
richeym
2010-07-03 12:19:42
+1 for the second sentence. It makes no sense to try out something else out of boredom - at the end relational databases are relational databases. The devil is in the detail (and sql server is a good one - not hard to keep running), but on a higher level they are all pretty much the same.
TomTom
2010-07-03 13:11:56
+1
A:
Define "good".
Do you want to have a database as a simple data store, or should the database also implement business logic (stored procedures, triggers)?
Do you want to ship your apps and therefore require easy of installation?
Does it matter if the database is commercial, when MSSQL offers a free version?
As @richeym pointed out: are SQL statement a sufficient interface, or do you require an ORM?
devio
2010-07-03 21:52:27