Re: Why use SQL Server
Plenty of reasons, though you wouldn't think of them if you're a small company and the only thing you care about is price. If I was an IT manager at a large company, this is what I'd be concerned about:
1. SQL Server has a proven track record. I've never even heard of Firebird until now, so I would have to do a lot of research and a lot of testing before putting it to real use.
2. Are there benchmarks comparing performance? Firebird is cross-platform and that *usually* means at least some hit to performance. Plus, I'm sure they perform differently with different tasks so performance-wise one might not be a right fit for what I'm doing.
3. Have any of my employees ever used Firebird? How difficult will it be for them to learn a new system? Keep in mind if I have to spend $30,000 training my employees on Firebird, I'm not really saving money.
4. How many new hires will have experience with Firebird? Tons of websites are built with PHP because tons of people have PHP experience. Far fewer are built with Ruby or ColdFusion because if your programmer leaves your hiring pool is limited.
5. How secure is Firebird? Can I hold the Firebird team accountable if we have a breach of security? Security bugs in SQL Server would be a huge problem for MS because they need to make money and no one will buy the product if it's not secure. A couple of open source developers don't have a business incentive to care.
6. Will Firebird be around in three years? Let's say the product is really good, but instead of eating Ramen for the rest of their lives the open source developers want to earn some money, abandon the project, and leave me high and dry.
And I'm not even an IT manager. I imagine someone that does this for a living could give you a dozen more reasons. And FYI, all open source software claims to be "robust, reliable and fast" (i.e. Android, which I've found to be rickety, unreliable and slow).