Well, if you are just reading from it then it might be a safe option.
1/2 the people will say MySql will die on you, and 1/2 wont. I will, since
I can't count the number of times we have had to recover the damn thing from
corruption caused by load, bad weather, and gnomes. Never had a single problem
with PostgreSql, so I would say go with that if the site is actually intensive
and you have a little time to learn about it.
But then again, many people run MySqlhell w/o problems. I guess it all depends
on what exactly you are doing with it. The times I have used it from .net
it wasn't a big deal, or particularly difficult to deal with, and now that
v5 is out it's a bit better. There definitly are a lot more tools, and much
more help, our there for it. PG is better in most respects, and _never_
worse, but mysql may do it for you.
If you are generating your database/data layer, then make sure your tools
support it. Many do not, and will only support mysql.
> Hi.
>
> For a currently smallish asp.net site we are running currently SQL
> Server Express.
>
> But the 4GB limit will be a problem sooner or later, and the licensing
> cost for a full blown SQL Server is just too high for such a small
> site.
>
> So, I am thinking about using MySQL for it (with the mysql .net
> driver: http://www.mysql.com/products/connector/ )
>
> So, is anyone using MySQL ado.net driver here too? Are there some
> known problems? How is the performance, and how well does MySQL work
> at all with .net?
>