MySQL vs SSIS

For smaller database backends, this product works well. Our backend printer management software is using MySQL as its backend and we have not had any issues since it went live 2 years ago. It's also free so no licensing worries.

I highly recommend this product. It has streamlined most business processes by providing useful tools that make work easier. The well-featured dashboard provides graphical integration services that have enhanced faster task and project implementation since it does not require coding. It has transformed data that could lead to poor performance into useful insights for generating new ideas for boosting business performance.

• Security: is embedded at each level in MySQL. Authentication mechanisms are in place for configuring user access and even service account access to applications. MySQL is secure enough under the hood to store your sensitive information. Also, additional plugins are available that sit on top of MySQL for even tighter security.
• Widely adopted: MySQL is used across the industry and is trusted the most. Therefore, if you face any problems, simply Google it and you shall land in plenty of forums. This is a great relief as when you are in a need of help, you can find it right in your browser.
• Lightweight application: MySQL is not a heavy application. However, the data you store in the database can get heavy with time, but as in the configuration and MySql application files, those are not very heavy and can easily be installed on legacy systems as well.

• Server Integration Services for SQL Server With the right planning of dataflows, we may aggregate information from many different sources.
• The solution's package structure allows us to isolate individual functions while reusing the same set of settings everywhere else.
• The capacity to test solutions in a variety of settings with varying inputs is a potent resource that facilitates the development of solutions that can be reused.

• Although you can add the data you require as more and more data is added, the fixity of it becomes more critical.
• As the demand, size, and use of the system increase, you may also need to change or acquire more equipment on your servers, although this is an internal inconvenience for the company.

• API connections are not a native functionality. We use Zappysys extensions but they work only in certain cases.
• Dependency executions - no simple way to create a hierarchy/chain of executions. Ex: Define if the execution of the child process should be stopped if a parent fails or a certain condition is triggered in the parent process and then redirect to a different part of the chain (think like a flowchart for executions).

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.

SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.

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.

SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.

SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.

The support staff is friendly, knowledgeable, and efficient. I only had to get part way through my explanations before they had a solution. They will walk you through a fix or actually connect in and fix the problem for you--or would if you can allow it. I've done it both ways with them. They are always forthcoming with 'how to do this if it happens again' information. I love working with MySQL support.

The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.

1. Estimate your data size. 2. Test, test, and test.

The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools

MongoDB is an application oriented solution with unstructured data. Percona Server for MySQL is a good solution when looking for performance peaks and the amount of data grows continuously over time. MySQL is the ideal solution when we have a data schema defined and we do not have great requirements at the performance level.

I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.

• It has made site management through a CMS like WordPress or Drupal infinitely easier to manage.
• It is a critical part of the LAMP, WAMP and MAMP stack and has been a major driver of innovation in the content-management-system space, pushing site and web-application development toward greater democratization.
• It has proved to be very reliable and easy to set up and administer and saves me tremendous time troubleshooting query and performance issues.

• Data integrity across various products allows unify certain processes inside the organization and save funds by reducing human labour factor.
• Automated data unification allows us plan our inputs better and reduce over-warehousing by overbuying
• The employee number, responsible for data management was reduced from 4 to 1 person