DBeaver - missing procedures in MySQL database - mysql

I have connected to my work database via DBeaver. Recently colleague told me about a procedure that lets me check newly added entities through our front-end.
And I can't find it in the list of procedures, nor using this query:
SHOW PROCEDURE STATUS WHERE Name LIKE '%name%'
I have the same connection settings as my colleague's, same user, etc, but he uses DbForge and I use DBeaver, cause at some point of time DbForge began having too much restrictions for free version (I wasn't simply able to execute queries), and the older version my colleague gave me didn't install in Windows 11.
So, I'm thinking may be there's some settings in the DBeaver that hide certain stored procedures, or I need to adjust connection settings.
Does anyone has clue on this?
Or may be someone could suggest some alternative to DbForge, which allows to execute queries in the free version and to set colors to connections (I find that thing convenient), and possibly doesn't have this problem, may be because of being more MySQl-oriented.
Thanks in advance!
I've tried to open connection settings and check out the additional parameters there, but can't seem to notice anything relevant.

Ok, seems like there was misunderstanding between me and my colleague, and he actually meant some another DB Server, but with same User/Password combination. Thanks for the comments, that also helped in finding the cause. I really did install MySQL Workbench, saw the same picture in there, and started wondering what else it could be and reading our communication again.
My mistake) The question is no longer actual.

Related

Forward engineer is doing nothing in the MySQL Workbench

I have little experience with MySQL Workbench and need some helps to figure out an issue. I loaded a new EER diagram from a .MWB file in the GUI and was trying to convert it into the SQL with Forward engineer. Initially, I was connected to the localhost and when, I press the Forward engineer..., nothing happens. The figure is as following, I'm working in the Mac OS Sierra operating system.
What I am missing here ? Some advice will help from the more expert users.
I use MySQL Workbench 6.3version for the work,
I've had this same issue with the latest release of MySQL Workbench (macOS). It's definitely some bug as previously, I didn't have any issues forward engineering.
Here's a workaround:
Normally, you'd go to:
Database > Forward Engineer...
To work around this bug, instead go to:
Database > Synchronize Model...
This will look for any open ERDs which do not currently exist with the rest of your schemas, and will allow you to forward engineer the schema that way.
Warning: This could get hairy if you had a lot of ERDs opened and didn't want to synch all of them, so make sure you've got the right ones checked!
I know this is a late answer, but this solution allowed me to forward engineer an ERD which previously was not firing (just as you described, nothing from MySQL Workbench).
I found your post when trying to find a solution, and while troubleshooting, heard via a personal anecdote about this work around. It may already be posted elsewhere on stack (tried to find link but couldn't find it), but hope this helps :)
Try:
File > Export > Forward Engineer SQL CREATE script

Unable to Resolve Symbol on SQL code (PhpStorm issue)

I am using PhpStorm 2016.1.2 and have been comfortably using PhpStorm for a couple of years. I have my Storm set up with the Database connection and displaying the MySQL database that my PHP pages connect to. The SQL is usually written within the PHP page in custom functions via a database connection class.
An example code chunk:
$checkData = $dataBaseSecure->getSelect(
"SELECT check_login.fail_id, UNIX_TIMESTAMP(check_login.last_action) AS timer
FROM check_login WHERE check_login.ip_addr = ? AND check_login.check_drop = ? ",
$data, TRUE);
Don't worry about the database PHP wrapper, this style and layout of SQL in PHP has been around on my work for a couple of years, in PhpStorm and works completely and accurately on the server and on all testings.
As Of Yesterday (17th June 2016)
I don't know what's changed but suddenly PhpStorm is now telling me, on all my SQL strings, across all my Projects:
Unable to resolve symbol '<table name>'
or
Unable to resolve column '<column name>'
And also (due to this) PhpStorm no longer carries out any auto-complete or organisation functions as I work on my SQL code.
Solutions I've tried
I have already tried to invalidate and revalidate my caches based on this answer to a similar question. But that hasn't helped.
I have very carefully explored my settings but the PhpStorm Database tab successfully connects to the database, and as far as I'm aware I made no changes to cause this change in behaviour.
I have looked over the various (and many) settings in PhpStorm preferences but seen nothing that has shone any light on this issue, or the changes I have tweaked have not resolved it.
I have found this answer but this does not seem to apply as my table names are not variables. I have also found this post, which while dated 2014 shows a similar issue but not a suitable solution.
I only have one database connection in most projects, but the number of databases doesn't seem to effect if this issue occurs.
Fully escaping SQL queries with appropriate backticks around named entities does not resolve the issue.
I have correctly configured my SQL dialect to the correct MySQL.
Reading related posts I'm found on Stack Overflow has provided no useful information.
I have no plugins in PhpStorm that relate to this issue or PHP/MySQL interaction.
If you have any ideas how to resolve this please tell me. If you have specific preferences you'd like me to check please let me know and I can add them into the question, (there are so many preferences in PhpStorm I won't post them all here right now, as I'm sure most are not related to this issue).
The Key is that this system was working perfectly two days ago!!!
Please try re-synchronizing your DB schemas -- just in case if it somehow got corrupted or invalid.
If it did not give any visual results -- try more radical version of it:
close IDE
open .idea subfolder for this project (the place where this project settings are stored)
delete dataSources.ids file
re-open project in IDE
re-sync DB structure / re-create DB connection from scratch.
None of the above worked for me - what eventually did was...
Selecting a portion of the SQL string that would run and then right clicking and selecting "Execute" and selecting the schema.
For some reason that allowed PHPStorm (more like light
drizzle) to figure out what it should be looking at.

Why is mysql workbench editor is so slow when working on a slow network?

I recently upgraded from Mysql workbench 5.x to 6.0.7.11215, And I am noticing strange slowness problem.
Whenever I try to edit the query, move the cursor around, or just try to add any characters, the editor hangs for a bit for a few seconds, and then resume normally.
This only happens when I am using a slow network connection to the server.
This issue was never there in the old Mysql workbench verison 5.x.
I disabled autocomplete, and restarted the program, but the issue is still there.
I used wireshark to examine the network traffic, and noticed a few of SSH packets at the time of the slowness, but I can't really know what is in them since, since the packets are encrypted. (it is worth noting that I am using database connection over an ssh tunnel)
I guess the slowness happens because of the context help. This feature queries the server's help tables to get help information for a specific topic that MySQL Workbench derives from the current caret position. Try this: hide the context help pane (activate snippet tab or hide the right side bar). If that context help pane is not visible no help queries are sent.
For more information about the context help see my blog post here: http://mysqlworkbench.org/2013/08/mysql-workbench-6-0-help-is-on-the-way/
work around: in the query place some extra comma by which the current line becomes x- in red colour
do all the editing ;
it won't go hang state
finally remove comma and execute
Set limit rows in query results to 1000 go in: Edit -> Preferences -> SQL Queries and check the limit to 1000
Workbench 6.1

How to load and execute query log on mysql server?

Hi i'm new on this site and i thank you all right now for the help you guys are hopefully going to give me. I am also new to the mysql enviroment. So, i have been told by my professor to find some tools which given in input log files (general or slow query) reproduces on a mysql server all the queries such as select, delete, update and insert. The tool should possibly be multi-threaded. I found something like mysql workbench or mk-log-player but i'm not sure if that is what i am looking for since as i have told before i'm new in the mysql enviroment.
I think You want Sql client for using Mysql
use SQL-yog client it is good for multiple connections to database.
you can download it from here
http://code.google.com/p/sqlyog/downloads/list

How do I reorder/clear the connection history in SQL Management Studio 2008?

I connect to a lot of different servers in SQL Management Studio, but I find that not only is there no way to delete the old connections (dbnames, usernames, etc.), they also start to show up as duplicates.
Is there any way to clear them/reorder the history? I can't seem to find any easy way.
Thanks!
I had the same issue and found the file in question is SqlStudio.bin. I'm not sure how you'd go about editing it, but if you re/move it, you get a blank slate for your SQL connections.
We still use XP here at work, so the file is located in the C:\Documents and Settings\%USERNAME%\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell folder.
Have a look at the DialogSettings.xml and mru.dat files in your %AppData%\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM directory. I haven't tried tinkering with mine yet, but they look like they've got the relevant information in.
I suggest you back them up first though!
If you just want to delete a connection you no longer need, select it in the Server Name dropdown and hit your delete key. Not particularly intuitive, but it works.