DBeaver offers comprehensive data management tools designed to help teams explore, process, and administrate SQL, NoSQL, and cloud data sources. DBeaver is available commercially as DBeaver PRO and for free as DBeaver Community.
$11
per month per user
SAP HANA Cloud
Score 8.9 out of 10
N/A
SAP HANA is an application that uses in-memory database technology to process very large amounts of real-time data from relational databases, both SAP and non-SAP, in a very short time. The in-memory computing engine allows HANA to process data stored in RAM as opposed to reading it from a disk which means that the data can be accessed in real time by the applications using HANA. The product is sold both as an appliance and as a cloud-based software solution.
SQL Server Management Studio (SSMS) developers should take a look at DBeaver to see how a real management studio application should be. In DBeaver you can tell that the developers really think about the way DBAs and database developers use database management tools. With SSMS, …
Verified User
Engineer
Chose DBeaver
MySQL workbench from MySQL only supports MySQL databases and it only provides basic functionality. On top of that, the user experience could be quite confusing for first-time users. SSMS from SQL server doesn't support inline editing nicely. The view for inline editing and view …
dbForge Studio has a more intuitive UI for die-hard Windows users. It's also easier to use sorting and filtering in their grids. However, that one lacked the script generation and schema editing tools our development team needed to use on an almost daily basis.
We have been using Microsoft SQL for our database related tasks until we made a successful & much-needed transition to SAP HANA for good. With the level of complexities SAP HANA can handle & deliver it was our obvious choice.
As SAP HANA is built into memeory, the proformance of the product is hard to beat against it's rivals but that comes with a price. You can get away with using another product but you'll be losing out else where. For example in time/multiple systems and efforts to relplicate …
The customer has most of their investment in Microsoft databases. If SAP HANA was not available, we would have gone to getting data into a SQL server and creating APIs to access them inside SAP. But, with the help of HANA, we could avoid all those unnecessary things and get …
The choice of the SAP HANA solution was mainly determined by the choice of the new company ERP, which having been SAP, naturally led to the choice of its DB solution.
SAP HANA is a more modern database with capabilities which reach far beyond a classical database. We chose SAP HANA as it represents the future direction of SAP which aligns with our strategic direction. With the introduction of S/4 HANA, SAP HANA will remain the only …
SAP HANA uses the sheer power of in memory analytics based on columnar compression of data in the back-end resulting in an overall decreased footprint of the data resulting in a paradigm shift. The traditional RDBMS database would rely heavily on additional indexes to retrieve …
There are many alternatives to SAP HANA if we consider functionality. Most of them, just like HANA, have their own niche place of specialization. But SAP HANA is at the forefront when it comes to performance comparison in its area of expertise which is business intelligence and …
If you are connecting to Snowflake and want to query from your laptop, I find that this is much easier to use than Snowflake's IDE. It allows us as a business intelligence team to more easily connect to our servers, and code with much less hassle. It would be less appropriate if you are only on an on-premises SQL server, in that case, I would just use SSMS.
I think if you have a large organization, it's probably the product and the marketplace to go to. We're a large management consulting firm operating in four to seven countries. And generally speaking, I think that's the size and the scope where it scales best. I can't speak to smaller companies, but I can't see smaller companies leveraging the benefits as much as a larger organization can.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
Real-time reporting and analytics on data: because of its in-memory architecture, it is perfect for businesses that need to make quick decisions based on current information.
Managing workload with complex data: it can handle a vast range of data types, including relational, documental, geospatial, graph, vector, and time series data.
Developing and deploying intelligent data applications: it provides various tools for such applications and can be used for machine learning and artificial intelligence to automate tasks, gain insights from data, and make predictions.
Schema editing is not very intuitive. Editing a single column forces you into multiple tab windows when trying to change something simple like a column name.
Sorting and filtering in data is nice, but buried in long right-click menus.
Some things are definitely non-standard UI for a Windows application, so it might be hard for die-hard Windows fans to get used to.
Requires higher processing power, otherwise it won't fly. How ever computing costs are lower. Incase you are migrating to cloud please do not select the highest config available in that series . Upgrading it later against a reserved instance can cost you dearly with a series change
Lack of clarity on licensing is one major challenge
Unless S/4 with additional features are enabled mere migration HANA DB is not a rewarding journey. Power is in S/4
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
We would rate our likelihood of renewing at 9/10. SAP HANA Cloud has proven to be a highly reliable and scalable data platform that consistently delivers strong performance. Its seamless integration with our overall SAP landscape, combined with improved analytics and real-time data capabilities, makes it a core part of our long-term technology strategy.
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
It is very useful solution which provides you speedier data processing, real-time analytics. It helps you manage diverse data types. It also offers you excellent disaster management. It has user friendly interface which helps you navigate system and transactions easily and perform task smoothly.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
Not a lot of users have DBeaver so fewer resources are available online to help you if you have any issues. When I was trying to figure out how to create my own ER diagrams, it was a little tough to find resources
However, I am not the right person to answer this as we have another department to handle support and contact the service provider for any support required. Although i will say that they are the quick respondent and knows how to handle querry of the customers and provide quick and better support.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Professional GIS people are some of the most risk-averse there are, and it's difficult to get them to move to HANA in one step. Start with small projects building to 80% use of HANA spatial over time.
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
MySQL workbench from MySQL only supports MySQL databases and it only provides basic functionality. On top of that, the user experience could be quite confusing for first-time users. SSMS from SQL server doesn't support inline editing nicely. The view for inline editing and view data is different, making it uncomfortable to use. All in all, DBeaver is the best tool when you manage a lot of databases with different types.
I have deep knowledge of other disk based DBMSs. They are venerable technology, but the attempts to extend them to current architectures belie the fact they are built on 40 year old technology. There are some good columnar in-memory databases but they lack the completeness of capability present in the HANA platform.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.