I am not very interested in the price difference between SQL Server and Oracle.
I need to deliver database performance and reliability to our Fund and stay within budget
Our annual SQL Licensing just went from under 200K to just over 600K.
Clearly this is not going to work for use and MSFT has just lost a customer that has had SQL Server for over 18 years.
I believe that you're not considering a huge set of costs. You'll have a huge amount of lost learning all the way from the Help Desk, through the Developers, up through the DBAs, and even with Managers and PMs. You'll also have to consider any impact you might have on your applications, backup systems, replication systems, DR systems, etc, etc, ad infinitum. True "Portability" between unlike RDBMSs simply does not exist even if your ORMs can handle it.
And, to be blunt, you shouldn't need 40 core to support "about 200 users" even on the worst day and changing RDBMSs isn't going to change that. Actually it might... depending on what you change you, you may, indeed, need 40 core depending on the condition of your code. ;-)
Whatever you decide, be very, very careful to fully identify ALL the hidden costs because they can be huge, indeed. Even something as simple as not having as many forums to go to can have a major impact in development costs (never mind the lost learning that I previously identified).
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs