Mysql Workbench Portable Zip
Kiliano Ratha
and click the lightning-bolt-with-cursor icon, the query starts, indicated by the spinner activating next to the "SQL File 4" tab in the following screenshot. However, the query doesn't complete and it just hangs. The white-hand-in-red-stop-sign icon is disabled.
I found that if you use the latest 6.3 version, that in order to get queries to work, you have open a first connection and ignore it and then open a second connection. This creates two tabs in the workbench. If you perform your queries in the second tab, it works. If you try in the first tab, it hangs.
I was getting around the problem for awhile by deleting the user library folder and dropping back to version 6.2.5 ... but today found the problem was back. So today I deleted the user library folder and dropped back to version 6.1.7. It's working again, for now.
That error doesn't make any sense to me. I'm able to open E:\Users\user_name\AppData\Roaming\MySQL in Explorer, so if I'm able to open that then E:\Users\user_name\AppData\Roaming\MySQL\..\ is clearly able to be opened as well.
I got this error "Could not read contents of..." when the laptop switched off all of a sudden when I moved the laptop a bit (battery loose connection problem) making Workbench and all applications closing unexpectedly, which is as good as the workbench getting crashed.
"C:\Users\YOUR.USERNAME\AppData\Roaming\MySQL\Workbench\sql_workspaces\YOUR_CONNECTION_NAME". Select proper folder names in your system, wherever I've used capital letters.First keep a backup of all the files inside that folder.
No matter whether the file is connection_id or whichever the file it is, if you see the file filled with "Null" or any illegal characters, close that file and delete such files These files are the culprit here which makes workbench to show the error.
I got this error when I renamed a connecteion.the old name was "new connection"when I renamed this back to "new connection" the error went awaythe workspaces are named according to the connection names
I ran into the same issue the minute I updated to Sonoma from BigSur (I know it's quite the jump), MySQL workbench connects to the server and it runs 2 queries until it crash and as to reopen. I use SQL for school just for reference. As you know Oracle hasn't released a version adaptable to Sonoma yet (I wish I had done my research beforehand), wasn't keen on downgrading but I found an alternative. Oracle has a MySQL Shell 8.0 extension for VS Code. It's not the same but works just fine for me, and if you're interested it also provides scripting capabilities for JavaScript and Python.
I think I have to trust in Oracle to bring with a compatible version soon, because the downgrade is not easy to do. Now I learned not to update MacOS in the next versions until is compatible with all my software.
When I look at the Workbench site I see that version 8.04 is compatible with Ventura (13) and Monterey (12). I don't see any mention of Sonoma. I do not use Workbench so can not do more research about your issue.
Then they probably shouldn't be using open-source or "community" software and/or upgrading their Mac. Those kinds of tools regularly break with operating system upgrades. I'm here to help people. But there isn't anything I can do in these cases.
Your suggestion to use an alternative, supported app is good. I don't know anything about this app. It appears to be regularly updated at least. That's laudable these days. I don't use any GUI database tools, so I don't have anything to recommend.
I had a similar problem with mysql-workbench package downloaded from dev.mysql.com (because MariaDB and Ubuntu's mysql-workbench package are incompatible) and a simple custom shortcut with the following launch command fixed the problem:
The problem is, I don't seem to have a mysqlcheck program anywhere. I'm using MySQL Workbench. It's possible I have used other MySQL versions in the past. When I look for mysql I find in the Program Files folder there is a MySQL folder with a MySQL Server 5.5 folder. This one has some .ini files and the bin, dat, etc directories, but no executables. Then in Program Files (x86) there is another MySQL folder. In that there are several folders including: MySQL Documentation 5.5.30, MySQL Installer, MySQL Notifier, MySQL Workbench CE 5.2.47, and Samples and Examples 5.5.30. The only one that has mysql.exe is MySQL Workbench CE 5.2.47. But it does not have mysqlcheck.exe.
My database is 17 GB and I removed some large text fields from large tables, and I'm hoping to recover space because my OS is yelling at me to make more space. Does Workbench have the capability to optimize, and if so how do I do it? And if not, what can I install to be able to do it?
I try connect database MySql workbench but de error: "Name or service not known" and the database postgres de same error (database is local and the hostname: localhost or 127.0.0.1), but I connect with powerbi and python is working.
"loacalhost" and the ip 127.0.0.1 is only reachable from within that very computer. It's a local name and a local IP that only exist in that computer. Or in any computer. For a cloud solution to be able to connect to a database on a local machine, the database must be exposed to the internet on a public address and not a local address (localhost and 127.0.0.1) are local addresses). -0-0-1-vs-localhost
This is not unique to Qlik Sense; nothing - no BI System or service - can connect to a local database on your computer (if the connecting system is not on your computer (by "your computer" I mean for example your laptop or other personal computer); Qlik Sense Desktop installed locally on your computer can probably use a local database).
But you are on the right track here in the image you posted now. If you have a public ip adress that can be reached from the outside world - and it seems you do - it can be possible to setup a connection that can access your database. But then there could be issues with what is called "ports", and you may need to set up "port forwarding" in your local router. Just because you have the public IP, a firewall (in your router and/or in your Windows settings) may block calls to your database. Among other issues you may encounter.
I can't say exactly what this means with your setup, but I'm guessing Qlik can't reach all the way to the db on your machine. As I said in my previous reply, there can be multiple reasons for that. I suggest you start by trying to connect to your db from another machine with a tool like for example MySQLWorkbench or DBeaver, preferably first on the same network and then over internet "from the outside" and make sure that you can connect properly. When you have managed to connect like that from another computer on the internet, you can start trying to connect from Qlik.
Before you can connect to a DB instance running the MySQL database engine, you must create a DB instance. For information, see Creating an Amazon RDS DB instance. After Amazon RDS provisions your DB instance, you can use any standard MySQL client application or utility to connect to the instance. In the connection string, you specify the DNS address from the DB instance endpoint as the host parameter, and specify the port number from the DB instance endpoint as the port parameter.
You can connect to a MySQL DB instance by using tools like the MySQL command-line client. For more information on using the MySQL command-line client, see mysql - the MySQL command-line client in the MySQL documentation. One GUI-based application you can use to connect is MySQL Workbench. For more information, see the Download MySQL Workbench page. For information about installing MySQL (including the MySQL command-line client), see Installing and upgrading MySQL.
To connect to a DB instance from outside of its Amazon VPC, the DB instance must be publicly accessible, access must be granted using the inbound rules of the DB instance's security group, and other requirements must be met. For more information, see Can't connect to Amazon RDS DBinstance.
You can use Secure Sockets Layer (SSL) or Transport Layer Security (TLS) encryption on connections to a MySQL DB instance. For information, see Using SSL/TLS with a MySQL DB instance. If you are using AWS Identity and Access Management (IAM) database authentication, make sure to use an SSL/TLS connection. For information, see IAM database authentication for MariaDB, MySQL, and PostgreSQL.
The connection information for a DB instance includes its endpoint, port, and a valid database user, such as the master user. For example, suppose that an endpoint value is mydb.123456789012.us-east-1.rds.amazonaws.com. In this case, the port value is 3306, and the database user is admin. Given this information, you specify the following values in a connection string:
To find the connection information for a DB instance, you can use the AWS Management Console, the AWS CLI describe-db-instances command, or the Amazon RDS API DescribeDBInstances operation to list its details.
To find the connection information for a MySQL DB instance by using the AWS CLI, call the describe-db-instances command. In the call, query for the DB instance ID, endpoint, port, and master user name.
To find the connection information for a DB instance by using the Amazon RDS API, call the DescribeDBInstances operation. In the output, find the values for the endpoint address, endpoint port, and master user name.
Only use an unencrypted MySQL connection when the client and server are in the same VPC and the network is trusted. For information about using encrypted connections, see Connecting from the MySQL command-line client with SSL/TLS (encrypted).
To connect to a DB instance using the MySQL command-line client, enter the following command at the command prompt. For the -h parameter, substitute the DNS name (endpoint) for your DB instance. For the -P parameter, substitute the port for your DB instance. For the -u parameter, substitute the user name of a valid database user, such as the master user. Enter the master user password when prompted.
4a15465005