I'm using MySQL Workbench and have had the following issue happen a number of times to me now.
If I'm altering a Stored Procedure, and workbench freezes or I need to restart workbench for whatever reason, then sometimes when I connect back to my DB, the stored procedure no longer exists.
I'm in Workbench 8.0.19 but same has happened in earlier versions as well.
Anyone have an idea why, or more importantly how to avert such happening?
Related
I am using MySQL workbench 6.3 CE to connect to mysql database on amazon aws (rds) system. I was running a create table query that was taking too long (lot of joins), and I stopped the query, and closed the workbench from Task Manager (end process). Since that operation:
1) I can open the workbench connect to the database, but once I connect and select any table from the schema, the workbench hangs.
2) No query could be run from workbench - I have to stop the query and I get the error "Interrupt: Error 2006, Mysql server has gone away".
3) if I click on the table name in the object browser, I don't see any columns for the table.
I tried to run the queries from the command line (in the workbench, right click on the database connection and click "Start command line client" - and here, I am able to run queries without issue. However, I have connected to this database through RODBC - in R, none of the odbcCommands are working (sqlTables() hangs, etc).
I am at my wits end trying to understand whats wrong - any pointers would be wonderful.
Thanks.
Actually, I realized it was because I stopped the create table query - I don't know the mechanics, but apparently, there was a background process running. I had to kill the query and kill the connection and everything was back to normal.
Hope this helps someone some other time.
I have encountered some unexpected behavior with MySQL server 5.6.26.
mysql is hosted on Windows 7 Enterprise 64-bit SP1.
I have a schema which contains some stored procedures. If I drop the schema and create it again the procedures still magically exist.
The stored procedures in question aren't visible in information_schema.routines nor mysql.proc.
The situation is even worse because when I try to drop the procedures with DROP PROCEDURE I get error that they don't exist (Error code 1305). On the other hand I am unable to create a new procedure with the same name (Error code 1304).
Restart of the service doesn't help.
I am interested in why is this happening. I can see the stored procedures listed in MySQL Workbench in the Navigator window. Where can possibly the stored procedures be kept?
This was fixed by running:
mysqlcheck --auto-repair -A -u username -ppassword
I have a freshly installed workbench 6.3 version and a 5.1 mysql Server version.
I already have connections created. Namely, I can successfully connecto to local Instance MySQL56, which I assume is a default connection. I have two, way older connections that have appeared even though last time I used this program (and later uninstalled) was months ago, with another version.
I've read what I've found and felt could help
MySQL Workbench 5.2 CE, Windows 7, "Can't connect to MySQL Server on 127.0.0.1 (10061)"
MySQL Workbench: "Can't connect to MySQL server on 127.0.0.1' (10061)" error
And tried every option. Nothing works. I try to create a connection with this steps:
Database -> manage connections -> bottom left corner: New
Then I give it a name, leave everything as default, put a pw into the vault, and try to test it. Does not work. Whatever combination I try, it does not work. Yes server is running, I've tried 3 different ways of checking.
I do not understand at all how something I've done in the past is taking me so many hours, I do not know what I'm missing, but I can't create a new connection.
Also to be noted, in case it's useful: On default schema, I write the name of a schema I previously created. Thing is, as I said, I've tried every combination. But when I've tried to save said schema in a folder, workbench has instantly crashed. Twice already.
I'm all out of ideas, so if anyone can tell me what to do, it'd be of great help, I find nothing following guides out there.
I recently had to reinstall MySQL. After doing so and restoring databases, I find that in one of my databases that the routines are not displaying in the object browser of Workbench. If I issue select * from mysql.proc in the query window, I do see all the routines. Also, my application that uses the routines has no problem running and accessing. I just can't see them any longer from the object browser in Workbench. I do see the routines of other databases but just one database is giving me the problem. Any suggestions on the problem here?
I upgraded to the latest version of MySQL and the routines now are showing again.
I've instaled MySQL workbench in Windows 7 64bit. Unfortunately, I'm facing problems:
In the Object Browser, when I click on my DB and right click on tables to create one, I can not insert any column (disabled) and therefore, can not insert tables. check this:
Can not create table in MySQL workbench 5.2.40
I can create table from the EER model. But even though, I faced problems when tried to connect my Java application to this database.
MySQL and Java: table doesn't exist
I have searched, and not sure from this, some of what I found is that workbench have probelms with Windows 7 - 64 bit (any idea if this is correct??). The only version I found was for 68, it installed successfully but I'm having probems.
I want to downlod MySQL server but before that: Will Mysql Server give me the same features that the workbench does? I need to work with GUI (insert, delete, update,..etc).
EDIT:
Also, the table I added using the EER are not visible in the Object browser. I only can see the schema in the Object browser without any table underneath it.
MySQL Workbench is a MySQL Server GUI. The two are different products. MySQL Workbench requires a MySQL Server connection for most tasks (except for data modeling). This reliance on a MySQL connection is clearer in the latest version of MySQL Workbench (6.1) than it was in 5.2.
MySql Workbench and MySql Server both are completely different things. MySql Server is basically a database and MySql workbench is a GUI or graphical management tool which helps us interact with MySql server database.
Similarly, SQL Server Management Studio is the graphical management tool for SQL Server.
Both are for manipulate the structure, queries and function, procedure, etc....
In Both you can Use DML and DDL
If you ask me I love Server even if you can create really cool designs on workbench, but basically you can do the same in both (insert, delete, update,..etc and more)
So it's up to you, I think MySQL server is a little bit lighter that Workbench, but if you want to, try it both.
Workbench looks like more friendly