MySQL Reviews

The primary use case for MySQL is to develop web applications, proof of concept projects with data collection, data manipulation, and data reporting on both Windows and Linux platforms. 

We also use MySQL to store the data that we receive from different projects and build data models. We can also develop reports out of it.

MySQL is used for small application use only and not used for enterprise-level business applications.

MSQL is free open-source software. This is the most valuable aspect for any company as it helps to reduce the cost.

MySQL is easy to use and, with basic knowledge of SQL, users can easily build SQL Statements. It helps to reduce project cost for development projects. It also supports a large number of embedded applications.

The backup and recovery features are easy to use without any complexity. Users who don’t have much knowledge of databases can easily use these features.

MySQL offers password encryption and offers a good data security layer to protect data.

MySQL platform independence helps the development and user community.

MySQL is a relational database and it is easy to install, handle day-to-day activities, and manage backups. It is compatible with a lot of other shared database solutions.

MySQL Workbench is the graphical user interface tool and it helps with development, data modeling, data migration, and day-to-day administration.

MySQL has cross-platform support for multiple operating systems. The backups on a Linux machine can be restored on a Windows machine, and vice versa.

MySQL supports multiple window displays and it is useful for developers and users who don’t have much database knowledge.

Improvements are required in character set support, scalability, and big data sets.

There is a lack of advanced features such as SQLServer, PostgreSQL, etc. I would like to see minimum reporting services and analytics features in the next release.

MySQL doesn't have many tools to monitor performance and fix issues easily.

The graphical user interface needs to be improved. It would be nice to have drag and drop on tables to create relationships between them. Other relational databases have these basic features. It helps during development to have these on hand.

It needs improvement in high availability and scalability features. 

I've used the solution for more than ten years.

MySQL is good for small to medium sizes. Also, it has built-in security features. 

The scalability is good.

The support may be limited for users who are not on cloud and needs improvement.

We did not previously use a different solution.

MySQL is easy to setup and offers HA and scalability features. 

We implemented the solution in-house.

Its free open source availability provides good ROI. MySQL commercial version cost is higher than other open source databases. 

MySQL is free open-source software. This is the most valuable aspect for any company. 

We looked at an SQL Server and Mongo DB.

It supports wide range of languages and cross-platform support. Also the newer versions of MySQL offers lot of new features. 

I have worked on migration projects between Power BI on Microsoft and SAP modules, which involve exchanging databases from Power BI on Microsoft to SAP modules. 

Additionally, I have been involved in integration projects as a MySQL developer using Oracle SQL databases.

MySQL has facilitated the migration projects to SAP modules from Microsoft Power BI, easing database exchange. The integration is smoother and more efficient, which has been beneficial for handling various projects.

The ML modules in MySQL are advantageous since they make data handling easy and quick at MNQM. I have a lot of experience with QA test sections on MySQL, and it aids in connecting with third-party programs effortlessly due to its adaptation capabilities.

MySQL has some unique exchange problems when it comes to migration projects. The product could improve in terms of security, though not necessarily when compared to Azure. It can be improved in areas related to database exchange during migration projects.

I have five years of experience with MySQL.

MySQL is stable and continuously improves concerning databases. It is advantageous for projects in this area.

Scalability in MySQL involves unique troubleshooting for every project that differs according to database exchanges. You can solve scalability issues easily if you possess strong SQL skills.

Technical support from Oracle for MySQL is very good. They are really good at providing support.

Positive

I have experience with Oracle SQL and have not used Microsoft SQL. MySQL and PostgreSQL are the tools I currently work with.

The initial setup for MySQL took about one and a half hours, and only one person was required for the installation.

Cost-saving is not a significant concern, but focusing on project details is crucial. The project details provide exchangeable areas that can lead to cost savings.

The pricing for MySQL is slightly expensive, especially in unique projects for sectors like automotive and pharmaceuticals. Despite this, it is preferable for special projects due to its unique offerings.

I have experience with Oracle SQL and PostgreSQL.

I'd rate the solution eight out of ten.

I use the solution for personal use cases like software development, mostly database bug systems.

I used the tool to build our website. It is used as a database to store information.

SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.

The full-text search feature must be improved.

I have been using the solution for the past three weeks.

I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.

I’m the only user in my organization.

The product provides good documentation online.

It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.

The tool is easy to manage and saves us time. It has much less complications.

We're using the community version. The tool is open source.

I also use PostgreSQL.

The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.

We use the tool in projects with customer records in the database. There will be a front-end application to search and find specific data from the tool. In another project, there are product listings, and the front end fetches data from the tool and shows it in a gallery or list view on the web page or mobile application.

We used MySQL in a project for a nonprofit museum. They have a lot of donors. They have a large repository of customers who give donations. They categorize the customers based on the money they give, such as steward level, platinum level, and diamond level. The client may send out an invite for an event for a certain group of customers, such as the patrons who donate the most. MySQL helped us in that project.

The optimized process is valuable. I have seen websites that take ages to load and show the data. Many web applications with lakhs and lakhs of data will take forever to show specific results. The database performance is optimal for the application we developed. The speed is very good. There were no delays in fetching data from the back end and showing it on the front end.

At times, the autoscaling does not happen when there is a surge in load. We had to depend on manual scaling. It led to website crashes in the past.

We have been using the solution for projects running for the past five years.

Scalability is one area in which we are very cost-sensitive. We always closely monitor the charges to increase the server scale. It will help us use more space in the DB if there is an economical way for us to pick up larger servers. We have more than six lakh end users.

Most of our projects are on the cloud. A very small number are on the client's premises.

We are continuing to use the tool because it's been cost-effective. It's producing revenue for us. It's a beneficial solution.

The tool is open source. We choose open-source software mostly. We integrate a very limited number of licensed software.

I have not seen any incident with a security violation or data breach. I have not contacted the technical support team. The infrastructure team contacts the technical support team regarding server-related issues. There is a LAMP stack. The Linux, Apache, MySQL, and PHP combination seems to be working well for enterprises' modern web applications.

Overall, the integration works well. However, initially, we worked with a third-party integration team to fix the APIs, query, and response code. Initially, some technical work will be needed. Once it is done, the integration turns seamless.

Overall, I rate the product an eight out of ten.

MySQL is easy and convenient for me. I don't need to rely on anyone. I can write the code and extract the information. It is fast if you know how to use it. The solution is not expensive, and most of the developers know how to use it. It is easy to create tables. The solution is stable and has good performance. The connection with AWS gives regular updates, which is manual otherwise and a nightmare. 

The tool needs to improve table visualization.

I have been using the solution for three years. 

MySQL is stable and fast. 

The tool is scalable. Around 15-20 developers use the tool in my company. 

MySQL's technical support is good. 

The tool's installation is easy. You must download the app and log in using a password and username. 

I rate the product a ten out of ten. 

Mostly, we're using it as a database behind a machine learning application.

For starters, it's free, which is always nice, and it's also pretty straightforward to use. It's a nice conventional database. We don't need the sort of flexibility that you get with most SQL databases and stuff like that, so we are happy with a good old-fashioned relational database. It's totally good for that.

It works. It's reliable. We haven't done any configuration management for probably about two years, but as far as I remember, that was pretty straightforward as well. It's doing what it needs to do as far as we're concerned.

The workbench could be improved. In particular, error messages can be improved, which are horrific and completely unhelpful. I'd like to see improved parsing of errors. When you write SQL and it crashes, it usually is something completely irrelevant and not helpful. I've started to use GPT 3.5 for finding out how to do things. I got to do something a bit different, and that I found to be very useful. If there was some way to tie it into one of the new AI tools, that would probably be a good idea. There were a couple of things that I've found difficult to do in the past, and I remember they were fiddly. I set them into ChatGPT, which is GPT 3.5, and it gave first-class answers.

I find it clunky. It just doesn't feel very modern. It feels as if you have to go through multiple steps to get to places, and it's not clear, but operationally, I find it fine.

I've been using this solution for about five years.

It's reliable. I never lost any data, which you anyways shouldn't. I'd rate it a ten out of ten in terms of stability because we never had the slightest problem. We are not in a challenging environment, but I haven't had any problems.

We've had absolutely no limitations. However, we haven't got enormous data. It's not very vast, so scalability hasn't been an issue. At our level, it's not even a question. It's absolutely perfect. I'd rate it an eight out of ten in terms of scalability, which I describe as very good

I've never contacted them, but technical support within the environment itself isn't good. I'd rate it a three out of ten, but now if I can use my own technical support with GPT 3.5, it comes up to about an eight out of ten. It's a kind of hybrid support.

We weren't using a similar solution previously. We would prototype from things like Excel or straight-off .TXT files. I had some experience and so did my business partner, and we just decided this looked like the right answer.

That was pretty straightforward as I remember. It was a while ago now, but I don't remember any difficulties at all. I'd rate it a nine out of ten in terms of the ease of setup. 

It's free.

We did look at MongoDB, but it wasn't what we needed, so we decided we go with something a little more conventionally established, and MySQL absolutely fitted the bill. We didn't need anything else. We got some colleagues who used Oracle, but it's expensive and quite difficult to use. 

If you don't have any unusual requirements or absolutely vast databases, it's ideal. We certainly have no problems at all. It just works.

Overall, I'd rate it a nine out of ten. Nothing is perfect, but it's as good as we could have asked for.

The solution is a database server. You can use it for desktop or web applications. The tool is used mostly for web applications. Most websites have MySQL databases behind them.

MySQL is an open-source product and has good community support. If you encounter any problem, you can easily ask other members of the community to help. They help you a lot. On top of being free, MySQL is a cross-platform database, meaning it can work on both Windows and Linux. It is very good for us.

The solution’s stored procedure is too light. MS SQL server supports stored procedures which MySQL doesn’t. Oracle and MS SQL servers support treiber which notifies you about data changes in the database. MySQL doesn’t support treiber.

I would like to see the automatic backup feature in the solution as well. Data is very important and we need to preserve it in a safe place. It would be good if MySQL can back up the data automatically.

I have been using MySQL for ten years. I use the solution’s latest version.

I haven’t seen any problems with the solution’s stability and I would rate the stability a ten on ten. It is a very stable tool.

I would rate the solution’s scalability a ten on ten. The tool is network-based and the scalability depends on the design of your project. You can use the product of both large and small-scale projects.

We are not a very large organization. There are around ten developers who use MS SQL server and MySQL for databases.

We are simultaneously using the MS SQL server and MySQL server. We first used MS SQL server and then in some projects, we required free and open-source databases. We use MySQL for those projects.

The installation was very easy and straightforward. The setup took around a couple of minutes which was five to six minutes to complete. The tool’s installation was really fast.

We didn’t require any assistance from third parties.

My company must have seen some benefit with the solution’s use.

I would rate the overall solution a nine out of ten. We didn’t find any issues in the solution’s maintenance. In every project, one developer would be in charge of their respective database maintenance. The solution has large community support.

MySQL is a fast database that is also high performing. When you want to do a project that requires a fast transaction, MySQL acts very well there. When a company needs a free database that is fast, could be connected over the network with many people, and do transactions, we usually suggest this solution.

We use MySQL for OLTP applications. HeatWave is used more on the SnowFlake and DSS side of the application.

Compared to other databases, MySQL is cheaper and we used the community edition which was free of cost. ML is fully integrated with the database in HeatWave. It also has many other features. MySQL is a far better solution in terms of pricing.

I would like to see more integrations of the solution with other platforms and improve the support on different data types.

I have been using the solution for more than 12 years. I am using the solution’s latest version.

I would rate the stability around seven to eight. They should improve the stability.

I would give a rating of eight out of ten for the solution’s scalability. We have a large user base for the solution which is more than 30.

MySQL is easy to set up if you have the PaaS service on your cloud infrastructure. If the setup is normal, then the overall deployment process is easier. However, if there is a need for clustering, then we will need an SME and assets.

You need to install an RPM on-premises to get the database. We need to tweak some parameters at the InnoDB. We have to create the cloud service on the Oracle cloud infrastructure.

The solution’s pricing depends on customer requirements. A license is not required for the community edition.

I would rate the overall solution an eight out of ten. However, compared to other open-source databases like PostgreSQL, I would rate it a nine out of ten. Compared to Oracle, I can give a rating of around seven to eight. We are using MySQL’s HeatWave. The maintenance of the solution is based on its complexity. In the normal scenario, one resource is good enough for maintenance and deployment. The older versions had an issue with stability. The issue has improved with the newer versions.