Yeesh, you're right, that's pretty bad. The assumption that the customer isn't going to need to update the database version (and thus shell out more...) in those 10 years invalidates the cost assumptions all on its own.
There's legitimate reasons to buy from the big three DB providers: there's a shortage of quality DBAs for postgres, and of course there are the 5-10% of cases that actually need the features/performance of the big 3. Evaluations like this, however, do not make a good case.
You need more than that. Comparisons and bullet points and blog posts aren't the problem here, there's already billions of those.
What's needed is more "PostgreSQL for SQL Server People" type conversion material and tools to help facilitate this process. NaviCat is not an acceptable solution here.
Years ago when I switched to MySQL it was because it was easy to get going, a lot of community support around the product. You have questions, you get answers almost immediately.
Postgres is a much more sophisticated offering and still needs to file down a lot of the sharp edges on their toolset. The psql command line tool for one is very bewildering to the uninitiated and has two conflicting syntaxes, one for the backslash commands and one for actual queries. This is not unlike other SQL shells, but MySQL, while highly non-standard, does have the advantage of a unified interface here.
Comments
What a fantastic example of false quantification and pretension to objectivity.
Yeesh, you're right, that's pretty bad. The assumption that the customer isn't going to need to update the database version (and thus shell out more...) in those 10 years invalidates the cost assumptions all on its own.
There's legitimate reasons to buy from the big three DB providers: there's a shortage of quality DBAs for postgres, and of course there are the 5-10% of cases that actually need the features/performance of the big 3. Evaluations like this, however, do not make a good case.
We need objective comparisons to promote PostgreSQL.
You need more than that. Comparisons and bullet points and blog posts aren't the problem here, there's already billions of those.
What's needed is more "PostgreSQL for SQL Server People" type conversion material and tools to help facilitate this process. NaviCat is not an acceptable solution here.
Years ago when I switched to MySQL it was because it was easy to get going, a lot of community support around the product. You have questions, you get answers almost immediately.
Postgres is a much more sophisticated offering and still needs to file down a lot of the sharp edges on their toolset. The psql command line tool for one is very bewildering to the uninitiated and has two conflicting syntaxes, one for the backslash commands and one for actual queries. This is not unlike other SQL shells, but MySQL, while highly non-standard, does have the advantage of a unified interface here.