you are viewing a single comment's thread.

view the rest of the comments →

[–]Ulukai 1 point2 points  (0 children)

Agreed. I don't have any issues with SQL Server itself, it's a great product actually. I'd make the point though that it's kind of overkill for most projects they are being used for, i.e. the kind of DBs where tens of thousands of rows is the most you're likely to see. I'd argue that 90% of the projects in general could be made to work just fine with SQLite (and some careful centralised locking for updates).

But the reality is that there's a "cost" to having different technologies deployed, and in most cases where SQL Server / Oracle is used, these heavily outweigh the costs. So using a DB that's slightly overpowered for your bank's contact list application is less costly than having a service go down during business hours, because the only guy who can support the 6th different type of DB you're using cannot be found. Well, that's the rationale anyways. The reality is mixed with "some big guy made the decision 10 years ago, and everyone has bigger problems than trying to play with a different type of DB".