RavenDB vs. Azure SQL Database

If you're a.NET developer searching for a system other than SQL Server for business assessment, then you must try RavenDB. RavenDB is a fantastic document-oriented system that has been specifically developed to work with all.NET or Windows systems. Developers are continually working on such systems to eliminate their flaws while also providing a few benefits. We must refresh ourselves on a regular basis since the free software system is like an open area where anybody may stand up with a brilliant solution to the issue. RavenDB is absolutely worth a look

Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.

Incentivized

• Document Database - no Object-Relational Impedance Mismatch
• ACID support that is optimized for performance
• Can be easily integrated into automated tests (unit tests)
• Easily configurable via C# code
• Comes directly with RavenStudio - no SSMS or SQL Developer required
• In general low footprint when it comes to memory and disk consumption
• Useful safety nets for new developers - e.g. by default an exception is thrown when you make too many requests within a session

• Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
• On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
• Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.

Incentivized

• The documentation is very good, but it's sometimes hard to find the topic I'm looking for.
• Updating references is done manually. It would be nice if there was a feature to help with that. I'm not sure that's even possible though.

• One needs to be aware that some T-SQL features are simply not available.
• The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
• No SQL Agent so your jobs need to be orchestrated differently.
• The maximum concurrent logins maybe an unexpected problem.
• Sudden disconnects.
• The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
• Only one Latin Collation choice.
• There is no way to debug T-SQL ( a big drawback in my point of view).

Incentivized

We've had an excellent experience using RavenDB. Internally we are testing the newer features in 5.0 such as time series, which will effect the con specified previously dependent on the real world performance. We foresee that BattleCrate will continue to use RavenDB as we grow.

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

Incentivized

Really good .NET client that is very easy to use. The management studio is excellent and puts anything that Microsoft or Oracle have to shame. Very quick to develop with once the complexity hurdle has been overcome. Initially using it can be a bit painful until you fully grasp the event sourced nature of the indexing.

It just works!

The support is really fast and flexible. Since one single working day, we got a response to our first request, only 4 days later we got a technical demonstration for our complete developer team to get in touch with raven and its performance. Also during our development, we got a quick response to questions.

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

Incentivized

RavenFS changed along the way and made us change the codes.

The given alternatives are also powerful and really good noSQL databases but the highest availability of RavenDB allows me/us to know it a lot better. RavenDB is encrypted by default wherever we use it in production and it has a high level of documents compression.

We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.

Incentivized

• RavenDB has saved my customers a lot of money with their cloud services' tiered model. The database is able to grow with the project/company and can start out small at a low cost.
• RavenDB is free for three nodes and three CPUs, which makes it great for development scenarios. You're able to start rapidly building applications without having to worry about licensing.
• Scaling out has allowed us to use three small cloud servers when starting out and get the performance and throughput of a single larger server.

• Perfect for small and medium databases, being very cost effective.
• As a Platform as a Service, there is no concern about patches, upgrades and end of life.
• Be aware of security and network capabilities. The service cannot run in the VNET as Azure Virtual Machines do.