Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost …
Rest all the big brand databases incure high licensing cost giving almost the same value that MySQL is giving being an open source database. Other databases like Oracle, MS SQL servers need extensive resource along with a huge team to manage those databases. However, thats not …
In terms of capabilities, Microsoft SQL Server is one of the leaders in the database market. It provides a lot of features for high availability, disaster recovery, performance and security. The primary reason why MySQL 8 was chosen was due to the open source nature of the …
Selection of MySQL or Oracle SQL Developer depends on various factors like timelines, requirements, features and data volumes. We are using both MySQL and Oracle SQL Developer in our organization. MySQL is more suited for small applications with few thousand TPS and less users. …
SQLite - Is the goto DB for Mobile/Desktop Apps. Its not as elaborate as Mysql but since its a RDBMS it provides all the basic features and its lite. We use mysql at the backend and for desktop app we use SQLite
postgres - Its a formidable opponent. It is fast and reliable and …
We chose MySQL because of its open-source nature and its compatibility with various systems, languages, and databases. It is easy to use and fast. Additionally, it has been in the market for more than 30 years now which makes it a reliable option when compared to its …
Our original implementation of MySQL was to replace an Access database that had unfortunately been able to grow beyond its abilities and scope. MySQL seemed to offer all the benefits of Access (easy to set up, use and administer) with none of the downsides (reliability, …
As I have been commenting in our company, we have solved our performance problems and responses obtaining speed in the queries occupies less disk space, in addition to its price and all the tools of great Scope it possesses.
The primary reason we use MySQL instead of MongoDB is because we are in a large, legacy enterprise environment. MySQL works well and has all the necessary integrations with the various other software tools in our company's suite. Additionally, MySQL is a relational database …
It was quite challenging to choose between these as they both have their pros and cons. But as far as we were concerned the decision to adopt the MYSQL database for our production was because it is an open-source language. This makes it very compatible with our needs and was …
MySQL is open source and reduces development costs drastically.
Verified User
Professional
Chose MySQL
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant …
MySQL works properly, it gives us the most efficient data and the organization of the data yields an unsurpassed result in performance. And in the same way, in our case as a company, we have users from different offices that are in the same line of work since they can share and …
Verified User
Manager
Chose MySQL
I have evaluated MySQL Heatwave for some ETL pulls in our database to generate reports for stakeholders. It helped me to do so.
Microsoft SQL and SQLite i have used for different scenarios. SQLite is very small database which is more easy to work with low profile devices like mobiles. MySQL is not suitable for that level and MSSQL mainly comparable with MYSQL. MSSQL has complex installations and …
So the main reason i would stack up Mysql from rest of the others is that it is open source which can be helpful for doing any POC on the products and learning new technologies and it is also compatible with all other softwares like Microsoft SQL serve and Postgre Sql
Having used both PostgreSQL and Microsoft SQL Server, I can tell that MySQL performs admirably in a Linux setting. When compared to Microsoft SQL Server, the extra benefit is the minimal or nonexistent licence fee. We find that MySQL's programming interface is particularly …
Higher levels of security and can handle multiple connections simultaneously which is required for our clients work. It also supports XML format which we've had issues with SQLite handling - doesn't appear to support it.
I would say that in a Linux environment MySQL works great compared to both PostgreSQL and MS SQL. The added benefit compared to MS SQL is the low or absent licensing cost. As we use it mainly from PHP the programming interface is great for MySQL. PostgreSQL has many of the …
I have also used Microsoft SQL Server. It is quite similar to MySQL. However, MySQL has always been my first choice, I have been using it for a very long time. I have also worked with PostgreSQL in a DevOps project. It is good too but a bit hard to learn and understand.
MySQL is relatively easier to use and than PostgreSQL or SQL Server; it's also cheap to use in production compared to SQL Server. For a beginner who wants to ship something quickly, MySQL is really suited for it.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.