New answers tagged mysql-workbench
I am getting the same error and I installed using MSI. Downloaded the VC redist packages for x64 and it fixed the issue: http://www.microsoft.com/en-us/download/confirmation.aspx?id=40784 Strange that the error message has python.exe as it's title..
You could make a start by using sed, awk and grep to change MySQL data types to SQL Server ones - but without a server to test on, you're really flying blind.
Well, I couldn't figure out how to do it in Mysql Workbench, but I have a workaround. Use: mysqldump -u mysqlUser -p DatabaseName TableName > table_data To get data out of the table you want to use, then use: mysql -u mysqlUser -p DatabaseName TableName < table_data To get the data into the desired table. This will retain the correct values.
You probably "installed" from the zip package, which does not do any validation of the available prerequisites for MySQL Workbench. I strongly recommend to use the Windows Installer (or at least the msi) which check if the VC++ 2013 runtime is installed (which includes the mentioned DLL). The installer also allows for easy upgrades and helps you with the ...
Since you get an "access denied" the actual connection to the server worked. You just have used a user that is not allowed to connect either because it connects from a machine that is not enabled in the user settings and/or the user does not exist or the password is wrong. Is it the correct server you connected to. Are you 100% sure to have used the right ...
Check for root user in mysql first. Set the password during first login and check if port and ip is added in /etc/my.cnf file. Hash the bind address and try again.
Use the Windows Task Scheduler or if you want to use the command line, then an at job should do the trick. On Window 7, the schtasks (see also here) should be of use. MySQL Workbench is not for doing this, except if you have the Enterprise Edition.
It would be better to use MySQL Workbench to write and test the scripts, but then use an OS-native script running utility to run the scripts at specific times. For example, on Linux you might use cron, which is simple to use (there are also tools designed to make it even easier).
You can see max_allowed_packet to 1G in your session SET max_allowed_packet = 1073741824; You can do so because MySQL will not immediately allocate it. A packet can grow. Please note how it mentions this in the MySQL Documentation: The packet message buffer is initialized to net_buffer_length bytes, but can grow up to max_allowed_packet bytes when ...
Top 50 recent answers are included