Frequently Asked Questions
Search through our knowledgebase for answers to questions you may be having about our solutions.
Yes, it is possible to integrate .NET applications with MySQL EE. As far as MySQL is concerned, any driver can be used, whether it’s EE or GPL.
Click Here for MySQL Connector/NET Developer Guide
MySQL seriously understands that Windows is the first and main development platform, and the work and time invested into MS products and solutions is far more than any other platform.
For more information that might be helpful:
MySQL Connector/NET 6.10.8 Release
MySQL Connector/J 8.0.12 Release
It’s easy to migrate database using MySQL EE Workbench. Some checks have to be done, but the main issue will be the code. Workbench does NOT migrate code. This is where the man-hours will be spent. There are 3rd party non-oracle promoted tools that can help migrate code here, like iSpirer SQLAnyways or similar, but careful here as they have tools that allow migration in any direction, i.e. from SQLServer to MySQL, MySQL-SQLServer, Oracle-SQLServer, etc. So we would be careful recommending this type of solution to only those really pro-MySQL users, who we know will always migrate from to MySQL. Also, these tools are costly.
MySQL Connector/NET 6.10.8 Release
MySQL Connector/J 8.0.12 Release
The key question here is, what happens when someone/some script/utility has to “move database to another server”.
If it’s a active-passive failover, i.e. the filesystem/cluster package that holds the datadir is moved to the other standby server, then that server will need secure access to the TDE associated key store or keyring wherever it is.
Ideally, Oracle licensing mentions that a subscription/license needs to be acquired when the software is “installed and running”.
If it’s a MySQL Replication scenario, the TDE keyring has zero impact because both servers would have an active keyring, that can be the same or different, as it’s totally independent.
If it’s a pure EE crash/disaster and no High Availability solution is implemented other than a pure Mysql Enterprise Backup (MEB) backup and restore, MEB will take the keyring key/configuration and once restored on a new server, that server will have to have access to the key store or have the keyring file in a secure and accessible location, and hence, no issue should arise.
Yes, it’s possible to do so, since there can only be 1 EE working at a single time. Moving from one server to another isn’t an issue in a Disaster & Recovery scenario.
Yes, it’s possible. In one sense, MEM has snmp event forwarding. Normally this is enough. It uses the MONITOR.MIB file in MEM.
The MEM agent uses LUA which can be configured to access via the Aggregator and hence act as a proxy to send traps & events to another system (this was how Query Analyzer works for v5.5 and previous instances that want to view the explain plans.)
There is also a way to access MEM without a user/pass using the JSON capabilities and an internal-to-MEM functionality via the following example URL: https://localhost:18443/v4/inventory/com.mysql.etools.inventory.model.mysql.MysqlServer/ whereby you have to change the value of localhost for the MEM repository/tomcat server. Using JSON you can create an API to read the output and push the events wherever you want.