Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by javery on Wednesday May 19, 2010 @06:48PM
(#1362638)
Using SQL Server Express is just trading one time-bomb for another time-bomb. Now instead of a 3 year bizspark timebomb we have a size time-bomb, once we cross that point we are springing for SQL Server. Why use a stunted Express product when you can use MySQL or Postgres for free?
[ Parent
| on HN ]
Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by redstripe on Wednesday May 19, 2010 @07:26PM
(#1362736)
Because it's a robust and feature rich database/tool-set thats great to develop on and gives me peace of mind. It's been a while since I used MySQL but the database and it's tools left me underwhelmed. I found that I could be more productive with SQL server. I haven't tried Postgres.
I guess I like to think if my databases grow too large for the free version that's a good problem to have. It's not that bad a "time-bomb" to me. Many sites will never need the paid version - especially the ones small enough to be so cost sensitive.
Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by javery on Wednesday May 19, 2010 @07:54PM
(#1362790)
You can't even do automated backups with SQL Server Express (without some hacks or other tools).
MySQL is a pleasure to work with and so it MongoDB, more so than SQL Server.
If you prefer SQL Server than more power to you.
Re:How We Moved From Microsoft ASP.NET to Rails and NoSQL
by redstripe on Wednesday May 19, 2010 @08:10PM
(#1362822)
I do backups using a windows scheduled batch file that runs sqlcmd.exe (part of sql express). Slightly hackish but it gets the job done.
Anyway, I hope that articles and interviews like yours do make MS lower the price of SQL standard, but people shouldn't dismiss the MS platform based on cost when in many cases it could be almost free.