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.
SAS Enterprise Guide is good at taking various datasets and giving analyst/user ability to do some transformations without substantial amounts of code. Once the data is inside SAS, the memory of it is very efficient. Using SAS for data analysis can be helpful. It will give good statistics for you, and it has a robust set of functions that aid analysis.
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.
Process time of data is a bit long. It depends on the size of your data and complexity of your project tree.
There is not enough online free training videos.
While working with the project tree sometimes the links between the modules are broken or the order for running the modules get mixed up. You should know your project tree by heart.
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.
It's not all bad, but I don't believe that an enterprise purchase of SAS is worth the expense considering the widely available set of tools in the data analytics space at the moment. In my company, it's a good tool because others use it. Otherwise, I wouldn't purchase a new set of it because it doesn't have some of the better analytical functions in it.
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.
Although I use SAS support for information on functions, these are SAS related and haven't really come across anything that is specifically for SAS EG.
I've not worked hands-on with the implementation team, but there were no escalations barring a few hiccups in the deployment due to change in requirement & adoption to our company's remote servers.
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.
Why I prefer SAS EG: Data processing speed is much faster than that R Studio. It can load any amount of data and any type of data like structured or unstructured or semi-structured. Its output delivery system by which we have the output in PDF file makes it very comfortable to use and share that file to clients very easily. Inbuilt functions are very powerful and plentiful. Facility of writing macros makes it far away from its competitors.
Positive (cost): SAS made a bundle that include unlimited usage of SAS/Enterprise Guide with a server solution. That by itself made the company save a lot of money by not having to pay individual licences anymore.
Positive (insight): Data analysts in business units often need to crunch data and they don't have access to ETL tools to do it. Having access to SAS/EG gives them that power.
Positive (time to market): Having the users develop components with SAS/EG allows for easier integration in a production environment (SAS batch job) as no code rework is required.
