-----BEGIN PGP SIGNED MESSAGE-----
Am 25.09.2016 um 11:12 schrieb Riaan Stander:
> Good day
> I’m leading the charge in our company to change our software
> product from SQL Server to PostgreSQL.
Having been exposed to SQL-Server for a while, all I can say is: good
> Our reasons are as follows:
> Cost: To use our product our self-hosted clients need to have SQL
> Server installed. None of them can afford the cost of Enterprise
> edition, limiting our ability to offer high availability
> Agility: When we want to use features in newer version of SQL
> Server we are in effect forcing our clients to upgrade, at their
> cost, to the latest version. This obviously does not go down well,
> limiting our ability to move forward.
> Our own hosting cost: Even for ourselves paying for SQL Server
> Enterprise in order to offer high availability is not a option.
> Given the above I’m proposing our company drop SQL Server and move
> over to PostgreSQL. Apart from technical features, which we are
> testing, business needs convincing to move away from something they
> know to something new.
> Can you point me to any marketing material, facts, use cases,
> white papers that can help state my business case.
I'd reckon your internal hosting costs should be enough to convince
your management. But alas, as most companies do their financial (and
effort) calculations in slightly different ways, you'll probably have
to do that math yourself...
I've got some more technical ammo for you though:
First, I very much like https://www.pg-versus-ms.com/.
Then, I've given a talk about basically what you miss when you stay
with SQL-Server at the pgconf.de 2015 (the slides are in english):
Hope that helps!
Gunnar "Nick" Bluth
Tel: +49 911/991-4665
Mobil: +49 172/8853339
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
-----END PGP SIGNATURE-----