MySQL Reviews

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.

Our company uses the solution to extract data from databases. We perform the create, read, write, and operations in databases.  

The number of users depends on the project. If there is a demand, then people good with SQL will jump in on projects. 

The solution helps us perform with our databases and extract data. 

The solution is free. 

Clusters are hard to perform so we use no SQL alternates like MongoDB. 

The solution should manage large data sets better because data that is around one lakh or two lakh fails to load. In these cases, we use no SQL structures like MongoDB. 

I have been using the solution for three years. 

The solution is stable. 

The solution is decently, but not largely scalable. It works very well and is comfortable with 50K or 60K of data. If you have large-scale data, then the solution is slower and has some errors. 

I have not needed technical support. 

The setup is pretty easy. All resources are available on YouTube so configuration is quite easy. 

We implemented the solution in-house and setup was pretty fast. You just set up the application, create queries, and connect with the front end or whatever you are trying to do. 

If you are handling large data, then it is a good idea to maintain the solution weekly because it will be better. 

The solution is open source so is free. 

The solution is good for smaller data or new users. If you are maintaining large data and want to build a fully-furnished application, then you have to use something else like PostgreSQL. 

If you are new to database management, then the solution will be the best choice. 

I rate the solution an eight out of ten. 

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.

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.

Positive

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. 

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.

I've used MySQL in the past for a variety of tasks. 

I once used MySQL when I created a PostgreSQL database for club management tasks. This included handling registrations, events, and mailing notifications for payments and event details. It served as a source service provider.

The response time for support could be faster. 

MySQL's performance requires attention. For optimal performance, one should review and sometimes revise the code, particularly when using server-side scripting. To optimize performance, it's crucial to pay attention to your code. Sometimes, you may need to review your code to ensure it's efficient and doesn't unnecessarily access the database multiple times.

The performance issues I encountered were not due to MySQL itself but were related to my coding approach.

I have been using MySQL for ten years. 

I would rate the stability a ten out of ten. 

For my use case, it is okay. Basically, it's just me for development. Previously, all clients or members of the club accessed it. When there was an event, maybe 30 to 40 people would try to access the system simultaneously.

I'm using SiteGround for hosting the website and its servers. I've chosen a package with more than enough CPU and memory to avoid trouble.

I've used technical support for several times. Most of the time, it was quite okay with quick responses. Once, I had performance issues. It took some time to convince them, but they guided me on improving performance by changing some database functions in MySQL. It was a longer process, but it was eventually resolved.

Positive

The initial setup was easy. I work in an agile way, which means coding and deploying quickly. We had a few internal users but many external users accessing the website, though not the back office.

The back office was developed over years. It's not just about having an idea and executing it; it's more about testing and adapting the process, unlike the waterfall method, where you end up with something that may not be immediately usable.

As the main user, our deployment process wasn't as strict as in a big company. I conducted tests, had a testing process with use cases to review, and then deployed. It was less rigid than in larger companies, where there are separate testing and development environments.

I  have seen value and impact from using MySQL

I don't pay for a license. 

With my previous employer, we used Oracle.

Don't just use MySQL on its own. Always use it with other software around it. MySQL is very stable, but pay attention to the software you use with it, whether you develop everything from scratch or use open-source systems like CMS.

Overall, I would rate the solution a nine out of ten. I would recommend using the solution. 

We use it for building web applications and managing data.

It is quite efficient and performs well, especially when compared to MSCS. While traditional scaling methods can occasionally lead to slowdowns, I haven't encountered similar performance issues with MySQL scaling.

The installation process for the most scalable solution is remarkably quick, taking only a short amount of time. While restoration may theoretically take longer, I've achieved rapid setup with my system, often within a minute.

While utilizing a comparable algorithm, is noted to be sensitive, especially when configuring the inner device. If DCDR is not properly recovered from NDC, it can lead to system slowdowns. There is a need for enhancements in the InnoDB cluster, specifically the capability to support more than two nodes in MySQL. Additionally, the inclusion of data nodes would be a valuable improvement. For users new to the system, it might pose a bit of a learning curve.

I have been working with it for one year.

I would rate its stability capabilities eight out of ten.

I would rate the scalability eight out of ten.

When facing support issues with your server, the level of assistance is generally high. However, in certain technical support instances, when issues are raised and a ticket is generated, the support team sometimes provides a link for further information. From a customer perspective, this approach is not ideal, especially when dealing with critical problems such as database downtimes. The expectation is for more direct and personalized support rather than reliance on knowledge-base resources in urgent situations.

Positive

I utilize Microsoft SQL Server (MSSQL) and MySQL for most of my databases. However, there are certain limitations in the new versions that impact support for certain functionalities. Due to these limitations, I have turned to MySQL as an alternative.

The initial setup was straightforward. I would rate it eight out of ten.

The deployment process, which took an hour, involves understanding various versions, especially the enterprise version, and confirming compatibility with the required features. Installation includes accessing the Oracle site, downloading MySQL, and dealing with complex considerations due to multiple business packages. Challenges may arise during the download of the DVD packet, requiring a careful assessment of the business needs for MySQL installation. The subsequent steps involve uploading MySQL VPN, reinstalling, and following a step-by-step approach, taking about five minutes. Despite the relatively swift deployment, managing dependencies and collecting necessary packets can be time-consuming and pose challenges for users. Maintenance requires only one person, especially if that person has knowledge of system administration. However, incorporating a software manager or other managing tools can be beneficial. Configuring and monitoring these tools doesn't necessarily require constant attention solely from the individual responsible for maintenance.

It is an open source platform. While the free version of MySQL offers comprehensive features, it does come with limitations.

Overall, I would rate it nine out of ten.

My primary use case for MySQL is with my products or websites for clients, and it helps me maintain relations with the best.

The relations in the database, the dynamic workflow, and the ability to connect with all columns. It's useful for e-commerce.

There is room for improvement in terms of the stability of the solution. 

I have been using MySQL for three years. 

I would rate the stability a seven out of ten. It does break down a little at times. 

I would rate the scalability a seven out of ten. 

The initial setup depends. For example, when working with e-commerce sites, it can be difficult to connect, and there may be failures. However, for other sites, it's easy.

Our organization is using MySQL by having it hosted through a hosting provider.

It is free. It is an open-source platform. 

Overall, I would rate MySQL a six out of ten. I recommend MySQL for small organizations and companies. For bigger organizations, one may need to consider other options.

You can also consider your project, budget, and organization while opting for MySQL. If it's a government or private project and what the product is.