We're a big enterprise primarily using SQL, and our production and disaster recovery setup is running on virtual machines. Recently, there's been more scrutiny on our database management, and the question of "what are our alternatives?" has come up. As I'm diving into this topic, I wanted to see if anyone has navigated similar waters before. What alternatives did you choose and how did that transition go?
5 Answers
It might help to clarify your question a bit. But just to throw out ideas, Excel can sometimes be used for smaller tasks, and NoSQL databases have gained traction. Your decision could depend on the purchasing and engineering culture in your company—there are many robust open-source options available!
SQLite paired with Litestream and S3 could work for lighter applications if you’re looking for something different. However, it's essential to identify your specific needs and use cases.
When looking for alternatives to Microsoft SQL Server, definitely check out PostgreSQL and MariaDB. There are plenty of good options out there. You can also refer to this list: [List of relational database management systems](https://en.wikipedia.org/wiki/List_of_relational_database_management_systems).
PostgreSQL is widely regarded as the closest alternative you’ll find for a reasonable price, especially with decent support. However, just switching out your database isn’t straightforward. If you're using advanced SQL Server features or reporting services, the transition won't be as easy as it sounds.
If you're specifically referring to Microsoft SQL Server, Oracle is a major alternative, but be prepared for some serious pricing there. Just a heads-up!
Or you could consider Oracle as a whole for a variety of services.
Please, let’s not give upper management any wild ideas about using Excel!